ZFS pool corrupted on upgrade of -current (probably sata renaming)

[Peter Schuller]

> Yep.  It's as simple as:
> 
>   * label all the drives using glabel, while they're still attached to the
> pool
>   * use "zpool replace pool ad4 label/disk01" to replace 1 drive
>   * wait for it to resilver
>   * use "zpool replace pool ad6 label/disk02" to replace the next drive
>   * repeat the resilver and replace until all the devices are replaced

While I can see this working "most of the time" - is there any reason
to believe it is guaranteed to? glabel keeps meta data at the end of
the device; is it guaranteed that ZFS is not using that part of the
device actively? (For example by having a policy to reserve some
amount at the end.)

-- 
/ Peter Schuller

PGP userID: 0xE9758B7D or 'Peter Schuller <peter.schuller at infidyne.com>'
Key retrieval: Send an E-Mail to getpgpkey at scode.org
E-Mail: peter.schuller at infidyne.com Web: http://www.scode.org

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20090715/4be749bd/attachment.pgp