[
https://issues.apache.org/jira/browse/DERBY-5232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13478388#comment-13478388
]
Mike Matrigali commented on DERBY-5232:
---------------------------------------
I second that the text located in the file should be generated from messages
file so that it can be translated.
I think it would be good if a file went into the log directory and into the
seg0 directory. Users can locate the log directory on a different device so
depending on implementation no note would
be associated with the log files if the file is not in the actual directory.
So maybe 3 files, one in seg0, one in log, and one in the parent directory.
It would be good if a backup/restore either copied the file or generated it to
get the same message to users looking at the backup and possibly corrupting it.
How about README_DONT_TOUCH_FILES.txt for file names?
As to content, seems like we should take the chance to be a little more
verbose. Something like:
For file in the log directory:
Do not touch files in this directory!
Files in this directory are used by the Derby database recovery system.
Ediiting, adding or deleting files in this directory will cause the Derby
recovery system to fail leading to unrecoverable corrupt databases.
For the file in the seg0 directory:
Do not touch files in this directory!
Files in this directory are used by the Derby database to store user and system
data. Ediiting, adding or deleting files in this directory will corrupt the
associated Derby database, and will not
be recoverable.
> 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
