On Sun, Apr 20, 2003 at 09:00:16PM +0100, John Bradford wrote:
> > > I know you favor a layer between low-level driver and fs
> > > probably. Sure it is clean design, and sure it sounds like
> > > overhead (Yet Another Layer).
> >
> > Wrong again - its actually irrelevant to the cost of mirroring data, the cost
> > is entirely in the PCI and memory bandwidth. The raid1 management overhead is
> > almost nil
>
> Actually what I was suggesting was even simpler - in the unlikely
> event that we were talking about an MFM or similar interface disk that
> _was_ basically like a big floppy, and did no error correction of it's
> own, we _could_ reserve, say, one sector per track, and create a
> fault tollerant device that substituted the spare sector in the event
> of a write fault.
>
> The overhead would probably be exactly zero, becuase nobody would
> actually compile the feature in and use it :-).
UFS used to do this because of MFM disks. In building a
filesystem you could provide a list of bad blocks and the
filesystem would maintian a block remap table. On Solaris
at least the reserved space is still required. By the time
most of the modern filesystems were created any hard disk
worth using in production had its own CPU and memory and
merely emulated a disk drive to the host while managing zone
recording and block remapping internally.
-- ________________________________________________________________ J.W. Schultz Pegasystems Technologies email address: jw@pegasys.wsRemember Cernan and Schmitt - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Apr 23 2003 - 22:00:28 EST