Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org Received: (qmail 82351 invoked from network); 26 Mar 2005 00:44:34 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 26 Mar 2005 00:44:34 -0000 Received: (qmail 96411 invoked by uid 500); 26 Mar 2005 00:44:31 -0000 Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org Received: (qmail 95873 invoked by uid 500); 26 Mar 2005 00:44:30 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 95860 invoked by uid 99); 26 Mar 2005 00:44:29 -0000 X-ASF-Spam-Status: No, hits=0.6 required=10.0 tests=DNS_FROM_RFC_ABUSE,RCVD_BY_IP,RISK_FREE,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: domain of oliver.zeigermann@gmail.com designates 64.233.184.197 as permitted sender) Received: from wproxy.gmail.com (HELO wproxy.gmail.com) (64.233.184.197) by apache.org (qpsmtpd/0.28) with ESMTP; Fri, 25 Mar 2005 16:44:29 -0800 Received: by wproxy.gmail.com with SMTP id 55so1425878wri for ; Fri, 25 Mar 2005 16:44:28 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=fpO2vOoCrfmvQdQfMlYabEGBOYjK6eWRJsd69nGhpiHe/FMPTYALRwShAB921wFHMO8Yflwp11+ebJ3nzlttzriLc6DnUSuiJWZW8Osjm9gLMz3uaRSMj3ZAZa4uHMW5vIEy5oJEndZwtlkWfqaJghqNViQ+4gi9trg7WdmOZdc= Received: by 10.54.29.67 with SMTP id c67mr695431wrc; Fri, 25 Mar 2005 16:44:28 -0800 (PST) Received: by 10.54.11.22 with HTTP; Fri, 25 Mar 2005 16:44:27 -0800 (PST) Message-ID: <9da4f45205032516442b0ab993@mail.gmail.com> Date: Sat, 26 Mar 2005 01:44:28 +0100 From: Oliver Zeigermann Reply-To: ozeigermann@apache.org To: Jakarta Commons Developers List Subject: Re: [transaction] FileResourceManager: "corruption" clarification please In-Reply-To: <20050325170842.15501.qmail@web26603.mail.ukl.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit References: <20050325170842.15501.qmail@web26603.mail.ukl.yahoo.com> X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N If both work and store directories are in the same file system to my knowledge there is no risk of corrupted data. At least when your OS supports atomic moves of files (most OS' do). Oliver On Fri, 25 Mar 2005 17:08:42 +0000 (GMT), Ricardo wrote: > hello devs, > > in the FileResourceManager doc it says > > "Important: If possible you should have the work and > store directory located in the same file system. If > not, you might get additional problems, as there are: > On commit it might be necessay to copy files instead > of rename/relink them. This may lead to time > consuming, overly blocking commit phases and higher > risk of corrupted files" > > assuming work and store directory *are* in the same > file system, what are the "risks" of corrupted files > (beyond os/hardware failure) ? > > do you have additional advise to make 100% sure > data is accessible after commit? > > thanks > ricky > > Send instant messages to your online friends http://uk.messenger.yahoo.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org > For additional commands, e-mail: commons-dev-help@jakarta.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-dev-help@jakarta.apache.org