Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Tue, 9 Apr 2013 01:35:13 +0000 (UTC)
From: "Myrna van Lunteren (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: <JIRA.12641507.1365471257630.131846.1365471313272@arcas>
In-Reply-To: <JIRA.12641507.1365471257630@arcas>
References: <JIRA.12641507.1365471257630@arcas>
Subject: [jira] [Created] (DERBY-6157) text for message XSLA4 might
 encouraging people to delete part of the transaction log
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Myrna van Lunteren created DERBY-6157:
-----------------------------------------

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