I just bumped from:
FreeBSD 7.2-PRERELEASE #1: Wed Mar 18 00:55:27 PDT 2009
to:
FreeBSD 7.2-STABLE #2: Wed Jun 10 18:27:30 PDT 2009
I rebooted and my zpool was WHACK'd. I was getting these errors in
/var/log/messages:
Jun 11 16:54:55 crepe3 root: ZFS: vdev I/O failure, zpool=tank
path=/dev/ad6s2c offset=481721292800 size=1024 error=5
Jun 11 16:54:55 crepe3 root: ZFS: vdev I/O failure, zpool=tank
path=/dev/ad6s2c offset=481721293824 size=1024 error=5
I had ad0s2 and ad6s2 in my zpool mirror, but after the upgrade zfs read
the devices as:
ad0s2 and ad6s2c.
So I dropped the 'c' parition and reattached the slice:
# zpool detach tank ad6s2c
# zpool attach tank ad0s2 ad6s2
and now my 'zpool status' shows it resilvering...
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 0h22m, 21.91% done, 1h21m to go
config:
NAME STATE READ WRITE CKSUM
tank ONLINE 0 0 0
mirror ONLINE 0 0 0
ad0s2 ONLINE 0 0 0 82.2M resilvered
ad6s2 ONLINE 0 0 0 19.0G resilvered
QUESTION: Why the heck would ZFS latch onto ad6s2c partition instead of
the ad6s2 slice? I've rebooted many times before without issue... it
seems the upgrade bonk'd things.
Hopefully when this is all done, I can run zfs upgrade... anyone have
trouble with "zfs upgrade"?
Rudy
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
