db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mike Matrigali <mikem_...@sbcglobal.net>
Subject Re: [jira] Commented: (DERBY-555) Unable to restart after disk is full
Date Mon, 19 Sep 2005 16:29:15 GMT
that seems reasonable.  Unfortunately for some of the errors like this
store gets an exception but java does not give us enough information to
know exactly why it failed so the code has to guess.

Øystein Grøvlen (JIRA) wrote:
>     [ http://issues.apache.org/jira/browse/DERBY-555?page=comments#action_12329831 ]

> 
> Øystein Grøvlen commented on DERBY-555:
> ---------------------------------------
> 
> Since it seems not to be possible to detect full disk in Java, my suggestion is to write
a message to derby.log when a database is made read-only which states that reason may either
be because it is lacking write access or because the disk is full.
> 
> 
> 
>>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
> 
> 
>>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.
> 
> 


Mime
View raw message