Date: Thu, 30 Aug 2007 15:56:35 +0900 From: Nathan Butcher <n-butcher@fusiongol.com> To: Christian Walther <cptsalek@gmail.com> Cc: freebsd-current@freebsd.org Subject: Re: Encrypted zfs? Message-ID: <46D66A23.3060108@fusiongol.com> In-Reply-To: <46D5B46D.5010202@gmail.com> References: <46D4EFFF.5080807@fusiongol.com> <46D5B46D.5010202@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> AFAIK zfs is immune against device enumeration issues itself. There is a > nice video on YouTube showing Sun engineers setting up a ZFS pool on a > bunch of USB sticks. Afterwards they remove all of them, shuffle them, > and put them back in. No problem. You're correct,... only as long as the zpool is EXPORTED FIRST, and imported after the drives have been shuffled around. ZFS has no trouble piecing them back together wherever they are during an import, it seems. If you were to, say, forget to export the zpool, shutdown your system, shuffle the drives around, and THEN restart the system with the drives in the wrong places, zfs will consider the zpool unavailable. In this case, all the drives will be turn up as FAULTED due to "corrupted data"... when in reality, ZFS was set up to expect certain data to be on certain drives, and now it just can't find it thanks to the harddrive "hokey-pokey" done on it. I guess glabeling isn't really necessary, but it does prevent the above issue from ever occuring.... "An ounce of prevention" or something like that.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?46D66A23.3060108>