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 proced
Reply-To:
Kudos to all of the people that came up with suggestions, patches and scripts.
In the end we managed to get the RAID up and running again, the funny thing
is that, instead of using the most recent drive and the last most recent one
we HAD to use the most out of sync and the last most r
[ It's great when you can pass on knowledge and other "see the light" and
pass it on in turn :-))
]
Whereas Tom has does it "for real" with his many GB of data depending on it, I
have never run a RAID5 array (other than 3 cylinders on a single disk!) so am
free to postulate from my ivory towe
Giulio Botto wrote:
> We have a similar problem on a 3way RAID5 with three different event
> counters on the three discs. We *KNOW* two of the are synced because
> power went off in seconds between the last two discs (sdc1 and sdb1),
> and we also know that sda1 is not synced because the logs show
