|
Re: Resizing raid-1 on replacing failed disk: msg#00193linux.raid
Guy wrote <snipped together from serveral replies>: You will be replacing your boot disk (I think). This will be a grub Thanks for your help! The array is not a boot disk (my bad - should have clarified)... But I do have other notes: * logically remove the failed disk - "mdadm /dev/md0 -r /dev/hdc1" Thank you for this extra detail! If you're partition is ext2 or ext3, you can use resize2fs. A word of And thanks again - this surely will help! It would perhaps be handy to have a tip on this (or more generally the resize array process) in the software-raid-faq (noting that e2fsck stuff is a file system rather than md issue). Perhaps I can contribute after completion. Please wait for someone to help with this! But not Could someone else please comment on the overall feasibility of resizing a raid-1 array to physically larger disks via this process? - backup> ** e2fsck -f - resize the ext3 partition Thanks and regards, matt - 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 |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | RE: Problem with RAID5 + ext3 expansion: 00193, Guy |
|---|---|
| Next by Date: | Re: Thanks :): 00193, Robin Bowes |
| Previous by Thread: | RE: Resizing raid-1 on replacing failed diski: 00193, Guy |
| Next by Thread: | Re: Resizing raid-1 on replacing failed disk: 00193, Neil Brown |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |