Date: Tue, 14 Jul 2009 15:50:47 -0700 From: Freddie Cash <fjwcash@gmail.com> To: freebsd-current@freebsd.org Subject: Re: ZFS pool corrupted on upgrade of -current (probably sata renaming) Message-ID: <b269bc570907141550u6854bc8eh6ea73fe9bd3e788a@mail.gmail.com> In-Reply-To: <alpine.BSF.2.00.0907142318520.2686@teapot.cbhnet> References: <alpine.BSF.2.00.0907132009040.2027@teapot.cbhnet> <alpine.BSF.2.00.0907142318520.2686@teapot.cbhnet>
next in thread | previous in thread | raw e-mail | index | archive | help
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. -- Freddie Cash fjwcash@gmail.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b269bc570907141550u6854bc8eh6ea73fe9bd3e788a>