Date: Fri, 31 Jan 2003 14:00:55 -0500 From: Steve Byan <stephen_byan@maxtor.com> To: David Laight <david@l8s.co.uk> Cc: phk@freebsd.org, freebsd-fs@freebsd.org, tech-kern@netbsd.org Subject: Re: DEV_B_SIZE Message-ID: <538478DE-354E-11D7-B26B-00306548867E@maxtor.com> In-Reply-To: <20030131185507.G1487@snowdrop.l8s.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Friday, January 31, 2003, at 01:55 PM, David Laight wrote: >> Really? fsck can recover from losing 4K bytes surrounding the last >> metadata block written? > > The only metadata that matter are the inodes and (for ffs) the > indirect blocks. You do really want the latter to be single disk > blocks - many systems actually write them synchonously. What could be the effect of losing surrounding blocks on the (failed) write of an indirect block? Can we guarantee that fsck can reconstruct the filesystem, modulo some recently-created or deleted files, or is there a possibility of losing the entire filesystem? > The inode is (probably) only 128 bytes, losing an inode block > will lose the other files. > > A journaling filesystem probably already has ways around this... I think journaling filesystems need to know the atomic block size in order to structure their log in a fault-tolerant way; I'm hoping someone on these lists can provide some details. Regards, -Steve -------- Steve Byan <stephen_byan@maxtor.com> Design Engineer Maxtor Corp. MS 1-3/E23 333 South Street Shrewsbury, MA 01545 (508) 770-3414 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?538478DE-354E-11D7-B26B-00306548867E>