[
https://issues.apache.org/jira/browse/DERBY-5232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13478464#comment-13478464
]
Kathey Marsden commented on DERBY-5232:
---------------------------------------
I think Mike's recommendations sound perfect for file names, contents (except
for typo: Ediiting) and locations. I think three files would be good as I
have seen in the past misguided instructions telling people to rm log/* or rm
-rf log without looking to see what's there. Mike, can you recommend wording
for the top level file. Perhaps in addition to mentioning the log and seg0
directory, it could also mention that service.properties contains critical
information about the format of the database and that the .lck files prevent
dual boot and corruption of the database.
Often when users embark down the deletion path, especially when it starts
with lock files, I find it is because of permission issues where multiple users
have booted (and perhaps modified) the database with inconsistent permissions.
What should have been done in those instances was the update the file
permissions to be consistent and what they want, but I don't know if it is good
to explain that in the top level file or if that is too much information.
> 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
> Attachments: DERBY5232_patch1_diff.txt, DERBY5232_patch1_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
