db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Francois Orsini (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-555) Unable to restart after disk is full
Date Sat, 03 Sep 2005 00:32:17 GMT
    [ http://issues.apache.org/jira/browse/DERBY-555?page=comments#action_12320945 ] 

Francois Orsini commented on DERBY-555:
---------------------------------------

There is no DiskFullException (working) exception in the current JVM - there are a couple
of JSR's (i.e. JSR-203) related to this as well as getting access to some extra FS api but
it is now planned for jdk 1.6 or possibly later (been requested for years)

There is a potential DiskFullException exception workaronud posted below:
http://weblog.janek.org/Archive/2004/12/20/ExceptionWhenWritingToAFu.html
(there is also an interesting behavior as far as file creation on a disk full - kinda skeptical
about that but eh)

There is also no API to return how space is left on a disk (device) - this is part of the
related JSR's as well...

--francois

> 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.

-- 
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