From: Jos Hulzink <josh@stack.nl>
To: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Cc: Mike Fedyk <mfedyk@matchmail.com>,
Helge Hafting <helgehaf@aitel.hist.no>,
<linux-kernel@vger.kernel.org>
Subject: Re: [Q] FAT driver enhancement
Date: Wed, 3 Apr 2002 14:21:56 +0200 (CEST) [thread overview]
Message-ID: <20020403140516.C38235-100000@toad.stack.nl> (raw)
In-Reply-To: <87y9g5m1zc.fsf@devron.myhome.or.jp>
On Wed, 3 Apr 2002, OGAWA Hirofumi wrote:
> Mike Fedyk <mfedyk@matchmail.com> writes:
>
> > > I mean I/O error, not data damage.
> >
> > It is the block layer's responsibility to retry such soft errors and recover.
>
> Yes.
But what about the data damage errors ?
> > 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.
How should the FAT driver know that the first FAT is bad if it doesn't
scan the FAT ? You don't want the second FAT to be used, you want the
mount to fail, and fsck.xxx to fix the mess. Who tells you that the second
copy of the FAT is the correct one, and not the first ?
Jos
next prev parent reply other threads:[~2002-04-03 12:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-28 13:25 [Q] FAT driver enhancement Jos Hulzink
2002-03-28 19:48 ` OGAWA Hirofumi
2002-04-02 9:34 ` Helge Hafting
2002-04-02 13:27 ` OGAWA Hirofumi
2002-04-02 22:13 ` Mike Fedyk
2002-04-03 7:07 ` Jens Axboe
2002-04-03 11:54 ` OGAWA Hirofumi
2002-04-03 12:21 ` Jos Hulzink [this message]
2002-04-03 12:45 ` OGAWA Hirofumi
2002-04-03 12:48 ` David D. Hagood
2002-04-04 0:06 ` Thunder from the hill
2002-03-29 23:11 ` Pavel Machek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020403140516.C38235-100000@toad.stack.nl \
--to=josh@stack.nl \
--cc=helgehaf@aitel.hist.no \
--cc=hirofumi@mail.parknet.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=mfedyk@matchmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox