Just to re-iterate for the googlers...
EVMS has an alternative raid5 grow solution that is active, maintained
and apparently works (ie someone who knows the code actually cares if it
fails!!!)
It does require a migration to EVMS and it has limitations which
prevented me from using it when I need
Hello all -
This is more of a cautionary tale than anything, as I have not attempted
to determine the root cause or anything, but I have been able to add a
disk to a raid5 array using raidreconf in the past and my last attempt
looked like it worked but still scrambled the filesystem.
So, if you'
I just come across an interesting situation, here's the
scenario.
0. Have a RAID1 array composed of two components, d1 and d2.
The array was running, clean, event counter was 10.
1. d1 failed (eg, hotplug-removed).
2. on d2's superblock we now have event=11, and d1 is marked
as failed.
3. the
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:linux-raid-
> [EMAIL PROTECTED] On Behalf Of Brett I. Holcomb
> Sent: Sunday, April 03, 2005 10:48 AM
> To: linux-raid@vger.kernel.org
> Subject: RE: Adaptec 3210S Problems
>
> Yes, sorry, there is a terminator block on the end of the
Hi !
Neil Brown schrieb:
Your best bet would be:
mdadm --create /dev/md2 --level 5 -n 4 /dev/hda1 /dev/hdk1 missing /dev/hdo1
and hope that the data you find on md2 isn't too corrupted. You might be
lucky, but I'm not holding my breath - sorry.
This worked AFAIS but there are troubles with the
