[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <49D0DAD3.6030507@rtr.ca>
Date: Mon, 30 Mar 2009 10:44:35 -0400
From: Mark Lord <lkml@....ca>
To: Ric Wheeler <rwheeler@...hat.com>
Cc: "Andreas T.Auer" <andreas.t.auer_lkml_73537@...us.ath.cx>,
Alan Cox <alan@...rguk.ukuu.org.uk>,
Theodore Tso <tytso@....edu>,
Stefan Richter <stefanr@...6.in-berlin.de>,
Jeff Garzik <jeff@...zik.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Matthew Garrett <mjg59@...f.ucam.org>,
Andrew Morton <akpm@...ux-foundation.org>,
David Rees <drees76@...il.com>, Jesper Krogh <jesper@...gh.cc>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Linux 2.6.29
Ric Wheeler wrote:
> Mark Lord wrote:
>> Ric Wheeler wrote:
..
>> The kernel can crash, and the drives, in practice, will still
>> flush their caches to media by themselves. Within a second or two.
>
> Even with desktops, I am not positive that the drive write cache
> survives a kernel crash without data loss. If I remember correctly,
> Chris's tests used crashes (not power outages) to display the data
> corruption that happened without barriers being enabled properly.
..
Linux f/s barriers != drive write caches.
Drive write caches are an almost total non-issue for desktop users,
except on the (very rare) event of a total, sudden power failure
during extended write outs.
Very rare. Yes, a huge problem for server farms. No question.
But the majority of Linux systems are probably (still) desktops/notebooks.
Cheers
--
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