[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

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.8.1.2
• Fix Version/s: 10.10.1.1
• Component/s: Store
• Issue & fix info: High Value Fix, Release Note Needed
• Assignee: Mamta A. Satoor
• Reporter: Katherine Marsden
• Created: 13/May/11 17:32
• Updated: 03/Sep/14 08:31
• Resolved: 13/Dec/12 16:26

Description

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.

Issue Links

• is related to: DERBY-5960 VirtualRandomAccessFile.close() is not idempotent
• is related to: DERBY-5995 Add a test case to check the 3 readme files get created even when log directory has been changed with jdbc url attribute logDevice
• is related to: DERBY-5996 Create readme files (cautioning users against modifying database files) at database hard upgrade time
• relates to: DERBY-5995 Add a test case to check the 3 readme files get created even when log directory has been changed with jdbc url attribute logDevice