Giulio Botto wrote:
> the feature I MOST would have liked in the situation I had at the moment was
> the possibility to update superblocks only and a tool which could read and
> let me write what I wanted in the various superblocks of the
> devices comprised in the array.
I agree that this procedure could be made easier if a tool existed to read the
current superblocks, suggest what should be done and write the superblocks
back out. I think that the lack of such an "easy" tool if partially because
in theory you shouldn't have to be going through this, that if you're more
than one disk down you have no data to recover. However, my own experience
indicates that this isn't the case. I've actually had to do this procedure
twice more since my first failure... as I have had some CRC errors with IDE
cables that kicked multiple drives out of the array. The codebase for
something like this would be almost identical to mkraid... maybe so much that
mostly what is needed is documentation changes to explain that this is
possible?
> All in all, I would have liked a tool like dumpe2fs or e2fsed to read the
> superblocks, and that mkraid had a nice --superblocks-only option.
I'm no expert, but after Piete explained this to me, I got the impression that
this is pretty much all mkraid does... write superblocks based on what is in
/etc/raidtab. Is this not true?
Congratulations on recovering your array. I know the feeling of bliss you can
get after being able to mount again!
Tom
