On Fri, 31 Mar 2000, Marc Haber wrote:
> On Thu, 30 Mar 2000 09:20:57 +0200, you wrote:
> >At 02:16 30.03.00, you wrote:
> >>Hi... I have a Raid5 Array, using 4 IDE HDs. A few days ago, the system
> >>hung, no reaction, except ping from the host, nothing to see on the
> >>monitor. I rebooted the system and it told me, 2 out of 4 disks were out
> >>of sync. 2 Disks have an event counter of 00000062, the two others
> >>00000064. I hope, that there is a way to fix this. I searched through the
> >>mailing-list and found one thread, but it did not help me.
> >
> >Yes I do. Check Jakobs Raid howto, section "recovering from multiple failures".
> >
> >You can recreate the superblocks of the raid disks using mkraid;
>
> I had that problem a week ago and chickened out after mkraid told me
> it would destroy my array. If, in this situation, destruction doesn't
> happen, this should be mentioned in the docs.
It _is_ in the docs. But the message from the mkraid tool is still sane,
because it actually _will_ destroy your data *if you do not know what you are
doing*. So, for the average Joe-user just playing with his tools as root
(*ouch!*), this message is a life saver. For people who actually need to
re-write the superblocks for good reasons, well they have read the docs so they
know the message doesn't apply to them - if they don't make mistakes.
mkraid'ing an existing array is inherently dangerous if you're not careful and
know what you're doing. It's perfectly safe otherwise. Having the tool tell
the user that ``here be dragons'' is perfectly sensible IMHO.
--
................................................................
: [EMAIL PROTECTED] : 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}...............:
