Return-Path: X-Original-To: apmail-db-derby-dev-archive@www.apache.org Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 13804D96D for ; Thu, 13 Dec 2012 16:26:15 +0000 (UTC) Received: (qmail 76045 invoked by uid 500); 13 Dec 2012 16:26:14 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 75540 invoked by uid 500); 13 Dec 2012 16:26:13 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 75132 invoked by uid 99); 13 Dec 2012 16:26:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Dec 2012 16:26:12 +0000 Date: Thu, 13 Dec 2012 16:26:12 +0000 (UTC) From: "Mamta A. Satoor (JIRA)" To: derby-dev@db.apache.org Message-ID: In-Reply-To: References: 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 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DERBY-5232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13531144#comment-13531144 ] Mamta A. Satoor commented on DERBY-5232: ---------------------------------------- Thanks for checking the release notes, Knut. I will go ahead and close this jira. > 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, releaseNote.html, 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: > 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