From owner-freebsd-fs Mon Mar 17 20:33:55 2003 Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E6CE137B401; Mon, 17 Mar 2003 20:33:53 -0800 (PST) Received: from bluejay.mail.pas.earthlink.net (bluejay.mail.pas.earthlink.net [207.217.120.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id 54A2C43F93; Mon, 17 Mar 2003 20:33:53 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0217.cvx22-bradley.dialup.earthlink.net ([209.179.198.217] helo=mindspring.com) by bluejay.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 18v8nG-00073H-00; Mon, 17 Mar 2003 20:33:43 -0800 Message-ID: <3E76A151.320A1E12@mindspring.com> Date: Mon, 17 Mar 2003 20:32:17 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Jeff Roberson Cc: Brooks Davis , Julian Elischer , Alfred Perlstein , FreeBSD current users , fs@FreeBSD.ORG Subject: Re: Anyone working on fsck? References: <20030317230147.I66343-100000@mail.chesapeake.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4797becd7d142051c76c6a303e25dd15f666fa475841a1c7a350badd9bab72f9c350badd9bab72f9c Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Jeff Roberson wrote: > On Mon, 17 Mar 2003, Terry Lambert wrote: > > Jeff Roberson wrote: > > > On Mon, 17 Mar 2003, Brooks Davis wrote: > > > > I am still intrested in improvements to fsck since I'm planning to buy > > > > several systems with two 1.4TB IDE RAID5 arrays in them soon. > > > > > > For these types of systems doing a block caching layer with a prefetch > > > that understands how many spindles there are would be a huge benefit. > > > > I call that layer "Vinum" or "RAIDFrame", since that's a job I > > expect that code to do for me. 8-). > > They are not responsible for data caching. Only informing the upper > layers how many spindles they have. Software RAID should be a transform > only in my opinion. There is no reason to have duplicate block caches in > system memory. Let's turn that around: "There is no reason to have duplicate spindle knowledge". Actually, I was not suggesting duplicate block caches, I was suggesting cache attribution by spindle by the code that knows what block lives on what spindle. 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-(. You would need a chain of spindle references, supplied by the code that knows the spindle, hung off the cache object. Gets ugly fast. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message