db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-5232) Put a stern README file in log and seg0 directories to warn users of corrpution they will cause if they touch files there
Date Tue, 11 Dec 2012 13:19:21 GMT

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

Knut Anders Hatlen commented on DERBY-5232:

Thanks for writing the release note, Mamta. Some suggestions:

The summary is supposed to be a one line, one sentence summary. What about "Derby will create
readme files in the database directories"?

I think the symptoms section should describe the symptoms seen when upgrading to the new Derby
release, not the symptoms seen when ignoring the advice in the readme files. For example:
"A database created with Derby 10.10, or upgraded to 10.10, will contain readme files named
README_DO_NOT_TOUCH_FILES.txt in the top-level database directory and in the subdirectories
seg0 and log."
> Put a stern README file in log and seg0 directories to warn users of corrpution they
will cause if they touch files there
> -------------------------------------------------------------------------------------------------------------------------
>                 Key: DERBY-5232
>                 URL: https://issues.apache.org/jira/browse/DERBY-5232
>             Project: Derby
>          Issue Type: Improvement
>          Components: Store
>    Affects Versions:
>            Reporter: Kathey Marsden
>            Assignee: Mamta A. Satoor
>             Fix For:
>         Attachments: DERBY-5232-kim.diff, DERBY5232_patch1_diff.txt, DERBY5232_patch1_stat.txt,
DERBY5232_patch2_diff.txt, DERBY5232_patch2_stat.txt, DERBY5232_patch3_diff.txt, DERBY5232_patch3_stat.txt,
DERBY5232_patch4_diff.txt, DERBY5232_patch4_stat.txt, DERBY5232_patch5_diff.txt, DERBY5232_patch5_stat.txt,
DERBY5232_patch6_diff.txt, DERBY5232_patch6_stat.txt, DERBY5232_patch7_diff.txt, DERBY5232_patch7_stat.txt,
DERBY5232_test_patch1_diff.txt, DERBY5232_test_patch1_stat.txt, DERBY5232_test_patch2_diff.txt,
DERBY5232_test_patch2_stat.txt, releaseNote.html, releaseNote.html
> Users often on bad advice or desperation  touch or delete files in the log or seg0 directories
(mostly log).
> I think it would be good for new databases and on upgrade that a file be created in these
directories with a name like:
> or some such to warn of the perils of doing this and the corrupting effects and how it
can eliminate any possibility of salvage. It should also encourage users to make a zip backup
of the database directory with no jvm currently accessing it before trying to do anything
with the database if it appears to be already corrupt.  Also point to backup/restore documentation
and encourage restore of a good backup into an empty directory if the database is corrupt.
> I'm not sure if it would help but it couldn't hurt.

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

View raw message