Date: Tue, 18 Mar 2003 14:59:51 +0100 From: Brad Knowles <brad.knowles@skynet.be> To: Terry Lambert <tlambert2@mindspring.com> Cc: Jeff Roberson <jroberson@chesapeake.net>, Brooks Davis <brooks@one-eyed-alien.net>, Julian Elischer <julian@elischer.org>, Alfred Perlstein <bright@mu.org>, FreeBSD current users <current@FreeBSD.ORG>, fs@FreeBSD.ORG Subject: Re: Anyone working on fsck? Message-ID: <a05200f08ba9cd68a00a6@[10.0.1.2]> In-Reply-To: <3E76A151.320A1E12@mindspring.com> References: <20030317230147.I66343-100000@mail.chesapeake.net> <3E76A151.320A1E12@mindspring.com>
next in thread | previous in thread | raw e-mail | index | archive | help
At 8:32 PM -0800 2003/03/17, Terry Lambert wrote:
> Even so, for RAID, this is generally problematic, because there's
> multiple locations for the block: where it lives, where it's mirrored,
> where it's parity block lives, etc.. Ideally, these are all different
> spindles, so the problem can't be fixed by a simple cache. 8-(.
It seems to me that there could be a logical cache which could be
provided by the RAID code, which would sit above the physical block
locations, the mirrors of the blocks, the parity data, etc....
Or is this the part that is provided by the filesystem?
--
Brad Knowles, <brad.knowles@skynet.be>
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
-Benjamin Franklin, Historical Review of Pennsylvania.
GCS/IT d+(-) s:+(++)>: a C++(+++)$ UMBSHI++++$ P+>++ L+ !E-(---) W+++(--) N+
!w--- O- M++ V PS++(+++) PE- Y+(++) PGP>+++ t+(+++) 5++(+++) X++(+++) R+(+++)
tv+(+++) b+(++++) DI+(++++) D+(++) G+(++++) e++>++++ h--- r---(+++)* z(+++)
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a05200f08ba9cd68a00a6>