> Hi Dave, > > I'm unclear about the autoreplace behavior with one > spare that is > connected to two pools. I don't see how it could work > if the autoreplace > property is enabled on both pools, which formats and > replaces a spare
Because I already partitioned the disk into slices. Then I indicated the proper slice as the spare. > disk that might be in-use in another pool (?) Maybe I > misunderstand. > > 1. I think autoreplace behavior might be inconsistent > when a device is > removed. CR 6935332 was filed recently but is not > available yet through > our public bug database. > > 2. The current issue with adding a spare disk to a > ZFS root pool is that > if a root pool mirror disk fails and the spare kicks > in, the bootblock > is not applied automatically. We're working on > improving this > experience. While the bootblock may not have been applied automatically, the root pool did show resilvering, but the storage pool did not (at least per the status report) > > My advice would be to create a 3-way mirrored root > pool until we have a > better solution for root pool spares. That would be sort of a different topic. I'm just interested in understanding the functionality of the hot spare at this point. > > 3. For simplicity and ease of recovery, consider > using your disks as > whole disks, even though you must use slices for the > root pool. I can't do this with a RAID 10 configuration on the storage pool, and a mirrored root pool. I only have places for 5 disks on a 2RU/ 3.5" drive server > If one disk is part of two pools and it fails, two > pool are impacted. Yes. This is why I used slices instead of a whole disk for the hot spare. > The beauty of ZFS is no longer having to deal with > slice administration, > except for the root pool. > > I like your mirror pool configurations but I would > simplify it by > converting store1 to using whole disks, and keep > separate spare disks.` I would have done that from the beginning with more chassis space. > One for the store1 pool, and either create a 3-way > mirrored root pool > or keep a spare disk connected to the system but > unconfigured. I still need confirmation on whether the hot spare function will work with slices. I saw no errors when executing the commands for the hot spare slices, but I got this funny response when I ran the test > Dave -- This message posted from opensolaris.org _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
