From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1G3gY3-0004aS-MO for garchives@archives.gentoo.org; Thu, 20 Jul 2006 21:59:12 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.7/8.13.6) with SMTP id k6KLvuIV011148; Thu, 20 Jul 2006 21:57:56 GMT Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.188]) by robin.gentoo.org (8.13.7/8.13.6) with ESMTP id k6KLrOvZ005127 for ; Thu, 20 Jul 2006 21:53:25 GMT Received: by nf-out-0910.google.com with SMTP id m19so650119nfc for ; Thu, 20 Jul 2006 14:53:25 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=ACGEQyjsfdbPvxcv9TEMOb1Imrx5aQOOOU4K6l/f/RPsKJjAg3nW124HRKxe18NM8F3fd26mffj36zVk4cpH7niXgxBnQEB5jy3nGO5rIy2qJYuduYMvg/o8qPrX2Koh5qEAdD/hg3w/7dTIwKl81Gw/011DBA3m+zePtg81V5Y= Received: by 10.78.156.6 with SMTP id d6mr958679hue; Thu, 20 Jul 2006 14:53:25 -0700 (PDT) Received: by 10.78.16.7 with HTTP; Thu, 20 Jul 2006 14:53:24 -0700 (PDT) Message-ID: <7573e9640607201453t4a96082bl6312c50780374c7f@mail.gmail.com> Date: Thu, 20 Jul 2006 14:53:24 -0700 From: "Richard Fish" Sender: richard.j.fish@gmail.com To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: amd64 installation: which file system? In-Reply-To: <1153427464.3839.155.camel@devilbox> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <7573e9640607181638w51ae2178p66721bf54e17de28@mail.gmail.com> <44BD7C15.8030600@vista-express.com> <44BD7DCA.2060903@gentoo.org> <1153271636.3839.80.camel@devilbox> <44BD8BA1.3080600@gentoo.org> <1153391863.3839.118.camel@devilbox> <1153393308.3839.123.camel@devilbox> <7573e9640607201114o624b56ddhf7eeb1cd5ee5b40d@mail.gmail.com> <1153427464.3839.155.camel@devilbox> X-Google-Sender-Auth: 1e1bc7572b25d1e6 X-Archives-Salt: 305616dc-0c77-4383-bf95-65b81afd8647 X-Archives-Hash: 7dff4a206f098931137d791dfe8014ca On 7/20/06, Cliff Wells wrote: > Well, the other "well-known" bit of info is that ext3 gets much of its > "reliability" from syncing every 5 seconds. If you want to use XFS and > get that sort of data reliability, here's a bash script to add to > rc.local: > > ( while true; do sync; sleep 5; done )& Well, you laugh, but my /etc/sysctl.conf contains: vm.laptop_mode = 0 fs.xfs.xfssyncd_centisecs = 500 > You can also mount XFS in sync mode if you are paranoid, but be warned > that it keeps your disks *very* busy. Yeah. I would rather use ext3 with data=journal! > So I guess the real question is this: what qualifies as "FS > reliability". Right. "Sucks" is imprecise in most circles. But consider this...the entire value of a filesystem is the files it contains. A filesystem that fixes itself by doing the equivalent of "mkfs" on reboot from a crash will be both completely consistent, and completely useless. By anyone's definition, it would "suck". > cross-linked files and bad inode counts). Also, having to fsck a large > disk array is going to be quite painful. Yes, ext3 maintainers are well aware of this. Have you seen: http://infohost.nmt.edu/~val/fs_workshop/ And the lwn article: http://lwn.net/Articles/189547/ -Richard -- gentoo-user@gentoo.org mailing list