On Tue, 14 Jul 2009, Freddie Cash wrote: > While I don't have any insight into how to repair this issue you've run into > (at least not off-hand), one way to mitigate/prevent this from happening is > to use glabel to label the drives, and then use the labels to create the > zpool. That way, it doesn't matter where the physical devices are located > in the system, nor what the physical device nodes are called, as zpool just > looks for the label, and GEOM handles all the heavy lifting/translating for > you. > > # glabel label disk01 /dev/ad4 > # glabel label disk02 /dev/ad6 > # glabel label disk03 /dev/ad8 > # zpool create pool raidz1 label/disk01 label/disk02 label/disk03 > > After that, you can shuffle the drives around in the system, and the pool > will continue to work correctly. Thanks - that was just what I was looking for! That'll save me an awful lot of hassle in future, especially as I'm eyeing up the CAM integration patch. In the meantime I'm successfully but slowly retrieving my data, I'll just have to be patient, but it's reassuring that I can build a new ZFS array with confidence. Cheers, Chris.Received on Tue Jul 14 2009 - 20:58:03 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:51 UTC