On Thu, Feb 07, 2002 at 06:35:16PM +0200, Cajoline wrote:
...
>
> In the past, I had a few incidents where the kernel complained about bad
> sectors on one of the disks in the array. However, since the filesystem
> on top of md0 is reiserfs, since there wasn't any tool for reiserfs to
> efficiently check/mark bad blocks, since doing a read+write test with
> badblocks on such a large filesystem is not efficient in itself (it
> takes hours for a few gigabytes, it would take many days for such a fs,
> and since it was only a relatively small number of blocks, I didn't do
> anything about it. If raidreconf comes across these sectors, reading
> from them may or may not fail, however writing on them will most likely
> fail. Would raidreconf crash under such circumstances? Or would it fail
> and continue with the conversion?
It shouldn't crash - but it will abort the conversion and exit.
I suppose that the "right" thing to do is to, for both reads and
writes:
Retry a few times, then just skip the block tagging it as "done"
...and print some good messages as well.
Is there a lot else to do ? The RAID layer will not re-allocate
blocks for you, so there's no way that raidreconf could move them
anywhere else and still have the filesystem (if any!) find them.
--
................................................................
: jakob@unthought.net : And I see the elder races, :
:.........................: putrid forms of man :
: Jakob Østergaard : See him rise and claim the earth, :
: OZ9ABN : his downfall is at hand. :
:.........................:............{Konkhra}...............:
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
