[
https://issues.apache.org/jira/browse/DERBY-6979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16272769#comment-16272769
]
Bryan Pendleton commented on DERBY-6979:
----------------------------------------
It seems like an interesting suggestion to me. I would suggest that it is a
feature, not a bug.
To be precise: are you saying that:
# Derby was up and running
# Your Derby filesystem filled up, resulting in the error shown in the text of
the Description of this issue
# Derby remained up, but was (of course) not able to process any work
# You made space available on the filesystem, by removing some other data
# You issued some more work to Derby
# Derby continue to report the exact same error as shown in the text of the
Description of this issue
Am I understanding your scenario accurately?
Was this with the Derby Network Server providing the Derby support? Or was it
an embedded application of your own?
Do you have the full Derby.log from the incident?
Can you reproduce this behavior?
I suspect this would be a challenging feature to implement reliably, partly
because a filesystem can fill at any moment, so there are many opportunities
for the problem to arise, and partly because testing on a system which is
completely out of resources is challenging.
Still, it seems like it would be a nice resiliency feature to have. Are you
able to work on this feature, to help with the implementation?
> Derby is still in read-only mode，even through I had released the disk space,
> and can't update data in database
> --------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-6979
> URL: https://issues.apache.org/jira/browse/DERBY-6979
> Project: Derby
> Issue Type: Bug
> Reporter: jiangchao
>
> I cleaned up disk and there are 80% of disk is freed for derby. But the derby
> is still in read-only mode:
> java.sql.SQLException: An SQL data change is not permitted for a read-only
> connection, user or database.
> org.apache.derby.impl.jdbc.EmbedSQLException: An SQL data change is not
> permitted for a read-only connection, user or database.
> org.apache.derby.iapi.error.StandardException: An SQL data change is not
> permitted for a read-only connection, user or database.
> Caused by: java.io.IOException: No space left on device
> at java.io.RandomAccessFile.writeBytes0(Native Method)
> at java.io.RandomAccessFile.writeBytes(RandomAccessFile.java:520)
> at java.io.RandomAccessFile.write(RandomAccessFile.java:550)
> at
> org.apache.derby.impl.store.raw.log.LogAccessFile.writeToLog(Unknown Source)
> at
> org.apache.derby.impl.store.raw.log.LogAccessFile.flushDirtyBuffers(Unknown
> Source)
> ... 23 more
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
