Talk:Growing
(Suggest stating that "expanding existing partitions" assumes single partition per disk) |
|||
Line 8: | Line 8: | ||
--[[User:Ivanbev|Ivanbev]] 13:13, 5 July 2008 (PDT) | --[[User:Ivanbev|Ivanbev]] 13:13, 5 July 2008 (PDT) | ||
+ | |||
+ | ---- | ||
+ | |||
+ | Expanding the size of an array while a write-intent bitmap is active can easily be fatal to the array. Trust me, I have the sleepless night to prove it. Neither mdadm nor the kernel code presently tests for this set of conditions when you attempt the --size=max; adding such a check and returning an error would be nice. | ||
+ | |||
+ | It is also helpful to explicitly show the wait for array recovery to complete before creating a write-intent bitmap, in case someone cuts-and-pastes the examples into a script. | ||
+ | |||
+ | It might be nice to use /dev/mdX consistently in the examples, instead of the occasional /dev/md0 and /dev/md1. | ||
+ | |||
+ | --[[User:CraigMiloRogers|CraigMiloRogers]] 12:58, 27 June 2009 (PDT) |
Revision as of 19:58, 27 June 2009
Under title expanding existing partitions, consider adding something like the following:
The below assumes a single partition per disk. If you have multiple partitions in different raid arrays (eg sdd1 in md0, sdd2 in md1 etc) then ensure you fail/remove and re-add all relevant partitions.
This is just so people don't forget to check whether they have multiple partitions on the disk they are about to remove!
--Ivanbev 13:13, 5 July 2008 (PDT)
Expanding the size of an array while a write-intent bitmap is active can easily be fatal to the array. Trust me, I have the sleepless night to prove it. Neither mdadm nor the kernel code presently tests for this set of conditions when you attempt the --size=max; adding such a check and returning an error would be nice.
It is also helpful to explicitly show the wait for array recovery to complete before creating a write-intent bitmap, in case someone cuts-and-pastes the examples into a script.
It might be nice to use /dev/mdX consistently in the examples, instead of the occasional /dev/md0 and /dev/md1.
--CraigMiloRogers 12:58, 27 June 2009 (PDT)