db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Øystein Grøvlen (JIRA) <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-555) Unable to restart after disk is full
Date Mon, 03 Oct 2005 14:20:50 GMT
    [ http://issues.apache.org/jira/browse/DERBY-555?page=comments#action_12331165 ] 

Øystein Grøvlen commented on DERBY-555:
---------------------------------------

If I understand you correctly, you suggest that I add an extra parameter to the boot message
that can be used to indicate that a database is booted in read only mode.  I can do that.
 I am a bit afraid that it will be less visible to someone inspecting the log file for the
cause of the problem, but I can write READ-ONLY in upper case :-)

I have now reproduce the same bug by setting the DB directory to read-only.  I will make a
test based on that.  Unfortunately, this cannot be added to derbyall before we can use J2SE
6 since there is currently no way to turn write access back on again.  Hence, you will have
to manually change the access rights in order to clean up the test directory after the test
has been run.

I will suggest a text to be added to the documentation.  Should I create a separate JIRA issue
for this?


> Unable to restart after disk is full
> ------------------------------------
>
>          Key: DERBY-555
>          URL: http://issues.apache.org/jira/browse/DERBY-555
>      Project: Derby
>         Type: Bug
>   Components: Store
>     Versions: 10.2.0.0
>  Environment: Sun Sparc Solaris, 1.4 JDK, Derby Client/Server
>     Reporter: Øystein Grøvlen
>     Assignee: Øystein Grøvlen
>     Priority: Critical
>  Attachments: derby-555.diff
>
> 1. Inserted data into the database until the disk was full. (5 clients inserting into
5 different tables in parallel.)
> 2. Shut down the server
> 3. Start the database again without freeing any disk space.
> When I try to start the database again, I get Null-pointer-exception, regardless of how
I connect (have tried embedded, client server, ij, jdbc applications).  I have not tried to
free some space on the disk before starting.  
> The call stack is not available right now (the computer I used had to be shut down due
to problems with our cooling system), but the exception comes from the following line in RawStore.java:
>      properties.put(Attribute.LOG_DEVICE, logFactory.getCanonicalLogPath());
> getCanonicalLogPath() returns null which results in a NPE in the hash table.
> A quick debug before the computer was stopped, showed that the logFactory was an instance
of org.apache.derby.impl.store.raw.log.ReadOnly which always returns null in its  getCanonicalLogPath().
> I suspect this may be related to the fact that I ran with the log in a non-default location.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message