Date: 15 Jul 2005 16:15:27 -0400 From: Lowell Gilbert <freebsd-stable-local@be-well.ilk.org> To: Matthias Buelow <mkb@incubus.de> Cc: John-Mark Gurney <gurney_j@resnet.uoregon.edu>, freebsd-stable@freebsd.org Subject: Re: dangerous situation with shutdown process Message-ID: <44br539674.fsf@be-well.ilk.org> References: <42D6B117.5080302@plab.ku.dk> <20050714191449.A8A615D07@ptavv.es.net> <20050714195253.GA23666@drjekyll.mkbuelow.net> <20050715185413.GI37261@funkthat.com> <20050715192928.GB1374@drjekyll.mkbuelow.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Matthias Buelow <mkb@incubus.de> writes: > The combination barriers+journal really seems to be very resilient > to filesystem corruption. When it's implemented without errors, and > the hardware doesn't do things like change bits randomly, I can't > think of a way this scheme can be corrupted at all. We keep trying to point out that barriers *can't* be enforced on the hardware with many (most, and apparently an increasing percentage of) ATA drives. There is no semantic on these drives that allows you to guarantee the journal block will be written before the corresponding data block. If you are sure that your drives do this properly, then you are safe, but in that case there's no reliability problem with softupdates, either.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44br539674.fsf>