Jonathan Schmidt wrote:
I just thought I'd let everyone know that the problem has been solved by
reversing the old and new raidtab files in the command line to raidreconf
(after fixing the bug that causes the immediate abort).
The old 4-disk array is currently running with the filesystem intact. I'll
go about backing it up now :)
"Jonathan Schmidt" <jon@xxxxxxxxxxxxx> wrote in message
news:dgckbo$her$1@xxxxxxxxxxxxxxxx
I just attempted to add a 5th 80GB disk to my RAID-5 array using
raidreconf. I previously added a 4th disk 6 months ago using the identical
tools with no errors or hiccups whatsoever. Back then, I made a full
backup because of all the warnings. This time, I assumed it would work
since it did last time, and did not backup the data. You can see where
this is going...
Here's some of the relevant info:
....
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Sweet.. :) I learn something new every day or every week on this list :D
I bet you are feeling like you tempted fate and won this round aren't
you? :P
Regards,
Tyler.
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.344 / Virus Database: 267.11.1/104 - Release Date: 9/16/2005
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
