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 685629EA4 for ; Tue, 22 May 2012 21:17:41 +0000 (UTC) Received: (qmail 16371 invoked by uid 500); 22 May 2012 21:17:41 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 16345 invoked by uid 500); 22 May 2012 21:17:41 -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 16333 invoked by uid 99); 22 May 2012 21:17:41 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 May 2012 21:17:41 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id 0855414282A for ; Tue, 22 May 2012 21:17:41 +0000 (UTC) Date: Tue, 22 May 2012 21:17:41 +0000 (UTC) From: "Kathey Marsden (JIRA)" To: derby-dev@db.apache.org Message-ID: <272845065.9546.1337721461036.JavaMail.jiratomcat@issues-vm> In-Reply-To: <729852461.30346.1334610137082.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (DERBY-5691) Document that Write Caching must be disabled to avoid possible database corruption 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-5691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281220#comment-13281220 ] Kathey Marsden commented on DERBY-5691: --------------------------------------- Thanks Kim, I Filed DERBY-5778 to test this scenario explicitly to see if it is a problem. I suppose it is ok to remove it until we have verified the problem. Certainly what you have added is a vast improvement and the Disable any other settings or options that might prevent a proper sync to disk will get people thinking about other options on the underlying disk that might cause problems. > Document that Write Caching must be disabled to avoid possible database corruption > ------------------------------------------------------------------------------------ > > Key: DERBY-5691 > URL: https://issues.apache.org/jira/browse/DERBY-5691 > Project: Derby > Issue Type: Improvement > Components: Documentation > Environment: Microsoft Windows > Reporter: Stan Bradbury > Assignee: Kim Haase > Labels: Write_caching > Fix For: 10.8.2.3, 10.9.0.0 > > Attachments: DERBY-5691-2.diff, DERBY-5691-2.stat, DERBY-5691-2.zip, DERBY-5691-3.diff, DERBY-5691-3.zip, DERBY-5691-4.diff, DERBY-5691-4.zip, DERBY-5691-5.diff, DERBY-5691-5.zip, DERBY-5691-6.diff, DERBY-5691-6.stat, DERBY-5691.diff, DERBY-5691.stat, DERBY-5691.zip, cadmindbintegrity.html > > > Suggestion that we document a recommendation that Windows Write Caching be disabled on machines using Derby. > The following article warns about Write Caching on Windows as a possbile source of database corruption: > http://support.microsoft.com/kb/281672 > It is possible that this could be the cause of some unexplained Derby corruptions identified after power failure of other system interupt. > Links explaining how to disable Write Caching: > Win 2K: http://support.microsoft.com/kb/259716 > Win 2008: http://support.microsoft.com/kb/324805 > From the Windows 2008 article: > With some third-party programs, disk write caching has to be turned on or off. Additionally, turning disk write caching on may increase operating system performance; however, it may also result in the loss of information if a power failure, equipment failure, or software failure occurs. This article describes how to turn disk write caching on or off. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira