[
https://issues.apache.org/jira/browse/DERBY-5232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13498404#comment-13498404
]
Mamta A. Satoor commented on DERBY-5232:
----------------------------------------
Hi Kim, thanks for taking the time to provide the feedback. I have changed the
wording of the readme files in messages.xml as per your suggestion. I would
like us to stay consistent with the error messages and use the term
NON-RECOVERABLE in the readme files. Also, to avoid the confusion and for the
text to look consistent, I have changed "Do not touch files in this directory!"
to all upper case. I will go ahead and commit these changes shortly.
> 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: 10.8.1.2
> Reporter: Kathey Marsden
> Assignee: Mamta A. Satoor
> Fix For: 10.10.0.0
>
> 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
>
>
> 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:
> TOUCHING_FILES_HERE_WILL_CORRUPT_DB_README.txt
> 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
