Date: Sat, 16 Jul 2005 12:16:57 +0200 From: Nicolas Rachinsky <list@rachinsky.de> To: freebsd-stable@freebsd.org Subject: Re: dangerous situation with shutdown process Message-ID: <20050716101657.GA44786@pc5.i.0x5.de> In-Reply-To: <200507152342.j6FNg5Tx015427@drjekyll.mkbuelow.net> References: <20050715224650.GA48516@outcold.yadt.co.uk> <200507152342.j6FNg5Tx015427@drjekyll.mkbuelow.net>
next in thread | previous in thread | raw e-mail | index | archive | help
* Matthias Buelow <mkb@incubus.de> [2005-07-16 01:42 +0200]: > David Taylor <davidt@yadt.co.uk> writes: > > >> A corrupted journal can be detected. If it's corrupted, discard > >> the whole thing, or only the relevant entry. The filesystem will > >> remain consistent. > >> If track corruption occurs after the journal is written, it doesn't > >> matter, since at boot the journal will be replayed and all operations > >> will be performed once more. > > > >The track which is corrupted could contain data that wasn't written > >to in months. How would the journal help? > > I don't understand this question. The track destroyed could contain sectors which are in no way related to the sectors the OS is writing to. Nicolas
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050716101657.GA44786>