On Mon, Mar 29, 2010 at 3:36 PM, John Robinson <john.robinson@xxxxxxxxxxxxxxxx> wrote: > On 29/03/2010 19:57, Doug Ledford wrote: >> >> On 03/29/2010 02:36 PM, John Robinson wrote: > > [...] >>> >>> Yes, but do create the partition(s), boot sector, etc and set up the >>> spare(s). >> >> Really, we should never have to do this in the situation I listed: aka >> no degraded arrays exist. This implies that if you had a raid1 /boot >> array, that it's still intact. So partitioning and setting up boot >> loaders doesn't make sense as the new disk isn't going in to replace >> anything. You *might* want to add it to the raid1 /boot, but we don't >> know that so doing things automatically doesn't make sense. > > Actually I've just recently had the scenario where it would have made > perfect sense. I hooked up the RAID chassis SATA[0-4] ports to the RAID > chassis and put 3 drives in the first 3 slots. Actually it turned out I'd > wired it up R-L not L-R so if I'd added a new drive in one of the two > right-hand slots it would have turned up as sda on the next boot. OK, to > some extent that's me being stupid, but at the same time I correctly hooked > up the first 5 SATA ports to the hot-swap chassis and would want them > considered the same group etc. This kind of situation is where an option-rom comes in handy i.e. the platform firmware knows to boot from a defined raid volume. However, it comes with quirky constraints like not supporting > 2-drive raid1. But I see your point that it would be nice to at least have the option auto-grow raid1 boot arrays. -- Dan -- 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
