> On Tue, Apr 02, 2002 at 10:27:52PM +0900, OGAWA Hirofumi wrote:
> > Helge Hafting <helgehaf@aitel.hist.no> writes:
> >
> > > OGAWA Hirofumi wrote:
> > > >
> > > > Jos Hulzink <josh@stack.nl> writes:
> > > > > Questions:
> > > > >
> > > > > 1) How do you think about the checking of the FAT tables ? It definitely
> > > > > will slow down the mount.
> > > >
> > > > Unfortunately if FAT table has bad sector, FAT tables may not be the
> > > > same.
> > >
> > > And then you don't want to mount unless you know what you
> > > are doing. And those knowing what they are doing can be bothered
> > > to use some kind of "force" option in this case. Or perhaps an
> > > option that selects which FAT to trust.
> >
> > I mean I/O error, not data damage.
>
> It is the block layer's responsibility to retry such soft errors and recover.
Yes.
> Probably the best you can do, is retry the read a few times if there
> is an error reported, and then fail if it persists.
Umm, there is a `copy of FAT table' for this kind of error. If the I/O
error occurs, the FAT driver should use the other FAT table.
-- OGAWA Hirofumi <hirofumi@mail.parknet.co.jp> - 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/