ZFS pool corrupted on upgrade of -current (probably sata
renaming)
Edho P Arief
edhoprima at gmail.com
Wed Jul 15 14:39:51 UTC 2009
On Wed, Jul 15, 2009 at 9:05 PM, Randy Bush<randy at psg.com> wrote:
>> # zpool status tank
>> pool: tank
>> state: ONLINE
>> scrub: none requested
>> config:
>>
>> NAME STATE READ WRITE CKSUM
>> tank ONLINE 0 0 0
>> mirror ONLINE 0 0 0
>> ad0p2 ONLINE 0 0 0
>> ad8p2 ONLINE 0 0 0
>>
>> errors: No known data errors
>> # zpool detach tank ad0p2
>> # glabel label disk01 /dev/ad0p2
>> # zpool attach tank ad8p2 label/disk01
> ^ huh?
>> # zpool status tank
>> pool: tank
>> state: ONLINE
>> status: One or more devices is currently being resilvered. The pool
>> will
>> continue to function, possibly in a degraded state.
>> action: Wait for the resilver to complete.
>> scrub: resilver in progress for 0h6m, 17.06% done, 0h29m to go
>> config:
>>
>> NAME STATE READ WRITE CKSUM
>> tank ONLINE 0 0 0
>> mirror ONLINE 0 0 0
>> ad8p2 ONLINE 0 0 0 60.7M resilvered
>> label/disk01 ONLINE 0 0 0 10.4G resilvered
>>
>> errors: No known data errors
>
> dfw0.psg.com:/root# zpool status
> pool: tank
> state: ONLINE
> scrub: none requested
> config:
>
> NAME STATE READ WRITE CKSUM
> tank ONLINE 0 0 0
> mirror ONLINE 0 0 0
> ad4s3 ONLINE 0 0 0
> ad5s3 ONLINE 0 0 0
> mirror ONLINE 0 0 0
> ad6s1 ONLINE 0 0 0
> ad7s1 ONLINE 0 0 0
>
> errors: No known data errors
> dfw0.psg.com:/root# zpool detach tank ad6s1
> dfw0.psg.com:/root# glabel label disk02 /dev/ad6s1
> dfw0.psg.com:/root# zpool attach tank ad6s1 label/disk02
> cannot attach label/disk02 to ad6s1: no such device in pool
>
attach to ad7s1.
Anyway, I find by using entire disk there's no need to worry about
this at all. The addresses are automatically adjusted upon change. (at
least in jbod mode)
--
O< ascii ribbon campaign - stop html mail - www.asciiribbon.org
More information about the freebsd-current
mailing list