[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090105114329.7973057b@lxorguk.ukuu.org.uk>
Date: Mon, 5 Jan 2009 11:43:29 +0000
From: Alan Cox <alan@...rguk.ukuu.org.uk>
To: Theodore Tso <tytso@....edu>
Cc: "Alexander E. Patrakov" <patrakov@...il.com>,
Pavel Machek <pavel@...e.cz>,
kernel list <linux-kernel@...r.kernel.org>,
Andrew Morton <akpm@...l.org>, mtk.manpages@...il.com,
rdunlap@...otime.net, linux-doc@...r.kernel.org
Subject: Re: document ext3 requirements
> If dm supported barriers, this wouldn't be an issue. Personally, I
"If the dm people applied the patches to support barriers" I believe is
the correct description - Andi ?
dm and md want fixing and even in the md case it isn't hard to do right.
> > or disabling write cache (but, as Alan Cox said, this
> > shortens the lifespan of the disk).
>
> Huh? I've never heard an assertion that disabling the write cache (I
> assume you mean using write-through caching as opposed to write-back
> caching), shortens the lifespan of disk drives. Aggressive battery
Thats what I was told by a disk vendor - simply because the drive makes a
lot more mechanical movements and writes.
> your noticing it, you can avoid running fsck at boot time. It's
> really more about shorting the boot time after a crash more than
> anything else.
That depends enormously on your environment. In a secure environment full
data journalling is practically essential to avoid the tiny risk of bits
of important data turning up in another users file.
Alan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists