db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kim Haase (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6157) text for message XSLA4 might encouraging people to delete part of the transaction log
Date Tue, 09 Apr 2013 20:40:17 GMT

    [ https://issues.apache.org/jira/browse/DERBY-6157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13627073#comment-13627073
] 

Kim Haase commented on DERBY-6157:
----------------------------------

The message is crystal clear and well written! It's much better than the previous one. It
should help to prevent the kinds of errors you mention.

My only suggestions are to change "read only" to "read-only" and to change "filesystem" in
the last sentence to "file system".
                
> text for message XSLA4 might encouraging people to delete part of the transaction log
> -------------------------------------------------------------------------------------
>
>                 Key: DERBY-6157
>                 URL: https://issues.apache.org/jira/browse/DERBY-6157
>             Project: Derby
>          Issue Type: Bug
>    Affects Versions: 10.10.1.1, 10.10.1.2, 10.9.2.2, 10.11.0.0
>            Reporter: Myrna van Lunteren
>
> This is not new, but while reviewing some of the 'disk full' messages resulting from
one of the long-running system tests, I realized that the text of ERROR XSLA4 could be read,
by people unfamiliar with derby and brave or in a panic, as suggesting one to delete parts
of the log directory:
> "ERROR XSLA4: Cannot write to the log, most likely the log is full.  Please delete unnecessary
files.  It is also possible that the file system is read only, or the disk has failed, or
some other problems with the media."
> We've been fighting people deleting files from the log directory, and even if this message
text may not be the culprit, it certainly is open for misinterpretation.
> I think we need to change this message. 
> English language experts and native as well as non-native speakers are particularly invited
to chime in.
> One suggestion is:
> Error encountered when attempting to write the transaction recovery log.  Most likely
the disk holding the recovery log is full.  If the disk is full, the only way to proceed is
to free up space on the disk by either expanding it or deleting files not related to Derby.
 It is also possible that the file system and/or disk where the Derby transaction log resides
is read only.  The error can also be encountered if the disk or filesystem has failed.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message