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.43) id 1E2Mpk-0002J9-Kp for garchives@archives.gentoo.org; Tue, 09 Aug 2005 05:39:29 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.4/8.13.4) with SMTP id j795cBYW013997; Tue, 9 Aug 2005 05:38:11 GMT Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.206]) by robin.gentoo.org (8.13.4/8.13.4) with ESMTP id j795Vvsr020410 for ; Tue, 9 Aug 2005 05:31:57 GMT Received: by zproxy.gmail.com with SMTP id x3so113421nzd for ; Mon, 08 Aug 2005 22:32:23 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=i1CnhmNIcILkXS4VUm8UNRWS/y37pnh5asMMfAg8Nbv1kHYpIsBcrRDFxWZ+JRqvejcC95jzmavpz1IRO26bXPmn2hVH7wqzIAzi0m6w46j6o1cgt1Qswjujtoft3EVDWHThMNniS+QnfQLDX9H9SGgtX+jarKvWEVMp7GZNptM= Received: by 10.36.148.6 with SMTP id v6mr711414nzd; Mon, 08 Aug 2005 22:32:23 -0700 (PDT) Received: by 10.36.7.13 with HTTP; Mon, 8 Aug 2005 22:32:23 -0700 (PDT) Message-ID: <558b73fb050808223266fe1120@mail.gmail.com> Date: Tue, 9 Aug 2005 01:32:23 -0400 From: Michael Crute To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Which filesystem for a notebook? In-Reply-To: <42F821EF.6050400@asmallpond.org> 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: multipart/alternative; boundary="----=_Part_3306_31734533.1123565543150" References: <42F7D154.7050106@mid.email-server.info> <200508090351.58660.volker.armin.hemmann@tu-clausthal.de> <42F821EF.6050400@asmallpond.org> X-Archives-Salt: 0f81f931-a575-4030-b41c-2ed3ae293931 X-Archives-Hash: d67ab53e0d7fce2e44b99bc9fdec0e89 ------=_Part_3306_31734533.1123565543150 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Personally I would use ext3 and then hdparm to adjust the drive settings so= =20 that it spins down faster when there is no activity. That should give you= =20 the best of power saving and data reliability. -Mike On 8/8/05, Richard Fish wrote: >=20 > Volker Armin Hemmann wrote: >=20 > >Hi, > >On Monday 08 August 2005 23:40, Alexander Skwar wrote: > > > > > >>Hello! > >> > >>What filesystem(s) do you recommend for use on a notebook? > >>I'm looking for a FS that's fairly stable even if all of a > >>sudden the power goes away (battery empty) and one, that > >>also doesn't (overly) unneccesarily spin up the hard drive. > >> > >>I don't think that I'll use Reiser4, as it's lacking an > >>online fs resizer. At least making the fs bigger should be > >>doable while the FS is mounted. > >> > >> > > > > > >I do not have any direct experience, but from all that I read over the= =20 > years I > >came to this: > > > >XFS is very fragile, when the power is failing. > >XFS will replace damaged files with zeros > > > >this is both not acceptable. > > > >Reiser4 is alpha code in motion. > >I would not touch it with a 10 feet pole at the moment. > > > >Well 4 filesystems left ;) > > > > >=20 > In the last year, I have run XFS, reiserfs v3, and ext3 on my laptop. I > mostly agree with you, although XFS doesn't really replace entire files > with zeros, just blocks that have been allocated but not written with > actual data...so /var/log/messages is likely to get some zeros in the > event of a bad crash. Files that were not being written at the time of > the crash are not affected. >=20 > Having run them all, my recommendation (and what I run currently) is > ext3. My soundbite summaries of each are: >=20 > XFS: aggressively caches, so might give you some power > savings...although real-world savings are likely to be slight to none. > Nice features (the only one that offers a free defragmentation utility, > even if it is brain-damaged). Cannot be shrunk, only grown. >=20 > Reiserfs V3: Excellent performance for _some_operations, slower > performance for others. Also can only be grown. >=20 > Ext3: Best journalling options available, including full-data > journalling if you want it and do not mind the slowness. Otherwise good > performance for the opposite operations as reiserfs. Can be grown or > shrunk. >=20 > I do not know of any Linux filesystem that can be resized while still > mounted. >=20 > -Richard >=20 > -- > gentoo-user@gentoo.org mailing list >=20 >=20 --=20 ________________________________ Michael E. Crute Software Developer SoftGroup Development Corporation "In a world without walls and fences, who needs windows and gates?" ------=_Part_3306_31734533.1123565543150 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Personally I would use ext3 and then hdparm to adjust the drive settings so that it spins down faster when there is no activity. That should give you the best of power saving and data reliability.

-Mike

On 8/8/05, Richard Fish <= bigfish@asmallpond.org> wrote:
Volker Armin Hemmann wrote:

>Hi,
>On Monday 08 August 2005 = 23:40, Alexander Skwar wrote:
>
>
>>Hello!
>>=
>>What filesystem(s) do you recommend for use on a notebook?
>>I'm looking for a FS that's fairly stable even if all of a
>&= gt;sudden the power goes away (battery empty) and one, that
>>also= doesn't (overly) unneccesarily spin up the hard drive.
>>
>>I don't think that I'll use Reiser4, as it's lacking an
>>= online fs resizer. At least making the fs bigger should be
>>doabl= e while the FS is mounted.
>>
>>
>
>
>I= do not have any direct experience, but from all that I read over the years= I
>came to this:
>
>XFS is very fragile, when the power is= failing.
>XFS will replace damaged files with zeros
>
>t= his is both not acceptable.
>
>Reiser4 is alpha code in motion.
>I would not touch it with a 10 feet pole at the moment.
>
= >Well 4 filesystems left ;)
>
>

In the last year, I h= ave run XFS, reiserfs v3, and ext3 on my laptop.  I
mostly agr= ee with you, although XFS doesn't really replace entire files
with zeros, just blocks that have been allocated but not written withactual data...so /var/log/messages is likely to get some zeros in the
= event of a bad crash.  Files that were not being written at the t= ime of
the crash are not affected.

Having run them all, my recommendati= on (and what I run currently) is
ext3.  My soundbite summaries= of each are:

XFS: aggressively caches, so might give you some power=
savings...although real-world savings are likely to be slight to none.
Nice features (the only one that offers a free defragmentation utility,=
even if it is brain-damaged).  Cannot be shrunk, only grown.<= br>
Reiserfs V3: Excellent performance for _some_operations, slower
p= erformance for others.  Also can only be grown.

Ext3: Best journalling options available, including full-data
jo= urnalling if you want it and do not mind the slowness.  Otherwise= good
performance for the opposite operations as reiserfs.  Ca= n be grown or
shrunk.

I do not know of any Linux filesystem that can be resized wh= ile still
mounted.

-Richard

--
gentoo-user@gentoo.org mailing list




--
________________________________
= Michael E. Crute
Software Developer
SoftGroup Development Corporation=

"In a world without walls and fences, who needs windows and ga= tes?" ------=_Part_3306_31734533.1123565543150-- -- gentoo-user@gentoo.org mailing list