Which gives me a RAID5 on 2x200GB (That right now really is a RAID1)
And I later on would like to add _another_ 200GB disk to that array and
turn it into a 400GB RAID5, can mdadm do that? I see a "grow" switch,
but I am abit unclear about the usage.
I think I'll be using XFS on that disk, which I understand _Can_ be
resized dynamically?
Re: obligatory mdadm.conf ? ... at least for the boot process.... This was a necessary step because the magic in use by mdadm... the array, reboot to raid, complete the array, synchronize, profit! ... a mdrun, creating the md devices (although i hear udev should do it from ... (Debian-User)
Re: [PATCH 000 of 5] md: Introduction ... >> By this I mean adding 1 or more drives to the array and then re-laying ... > three active drives and one spare. ... I'm not an mdadm guru, so there may be a method I overlooked. ... > which subsequently attmpted to access the array hung as well. ... (Linux-Kernel)
segfault mdadm --write-behind, 2.6.14-mm2 (was: Re: RAID1 ramdisk patch) ... I can create and use the array with: ... attach them with losetup and try to create the array with mdadm:... To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ ... (Linux-Kernel)
Re: remove/replace a harddisk in a unsynced raid1? ... > Your array was probably built with 2 RAID devices so anything else will ... > array with mdadm. ... Docs for mdadm are still rare and from the manpage ... is definitely a good idea to get a more consistent backup.... (comp.os.linux.misc)
