From owner-freebsd-questions@FreeBSD.ORG Wed Jul 23 08:38:46 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 923FD37B401; Wed, 23 Jul 2003 08:38:46 -0700 (PDT) Received: from mta1.adelphia.net (mta1.adelphia.net [64.8.50.175]) by mx1.FreeBSD.org (Postfix) with ESMTP id 18C9C43F85; Wed, 23 Jul 2003 08:38:45 -0700 (PDT) (envelope-from wmoran@potentialtech.com) Received: from potentialtech.com ([24.53.179.151]) by mta1.adelphia.net (InterMail vM.5.01.05.32 201-253-122-126-132-20030307) with ESMTP id <20030723154446.EHKZ7825.mta1.adelphia.net@potentialtech.com>; Wed, 23 Jul 2003 11:44:46 -0400 Message-ID: <3F1EAC04.10204@potentialtech.com> Date: Wed, 23 Jul 2003 11:38:44 -0400 From: Bill Moran User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3) Gecko/20030429 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Attila Nagy References: <3F1E6456.9090400@fsn.hu> In-Reply-To: <3F1E6456.9090400@fsn.hu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: questions@freebsd.org cc: current@freebsd.org Subject: Re: maildir with softupdates X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jul 2003 15:38:47 -0000 Attila Nagy wrote: > Hello, > > Is this statement still valid? > > "ext3 is unsafe for maildir, and with softupdates, so is ffs." > http://www.irbs.net/internet/postfix/0202/0358.html Yes, It's also true that any form of write-caching is unsafe, so disable the caches on your SCSI and ATA hard drives. Simply accept the terrible performance hit if you want super-reliability. Also, make sure you have redundant power supplies, UPSes and a diesel generator out back to cover power problems. In reality, anything comes with a certain amount of risk, and that statement is too vague to be useful. To my knowledge, ext3 is not unsafe by nature, it is simply unsafe by default because the default mount is async - which will generally be corrupted in the event of hardware failure. UFS+softupdates generally survives hardware failure without corruption, although it has a funny habit of losing files that were saved right before the failure. Result being that you could lose emails. However ... even a sync mount can become corrupt in the event of hardware failure, although it's much less likely. So you need to determine the risk level you're willing to accept as well as the performance you require. And you probably need to do more research than accepting that one-line statement, as it's too vague to properly describe the potential risk/benefits. This reminds me of the days when DOS first got disk-caching via a TSR (what was the name of that thing) and all the IT folks kept saying "Don't use it, it's dangerous" without understanding why it was dangerous. I used it anyway, because it improved performance considerably. Also, this is off-topic for -CURRENT, please remove -CURRENT from the CCs if you respond. I'm redirecting to -QUESTIONS for future discussion. -- Bill Moran Potential Technologies http://www.potentialtech.com