Yesterday, Paul Archer wrote:
I estimate another 10-15 hours before this disk is finished resilvering and
the zpool is OK again. At that time, I'm going to switch some hardware out
(I've got a newer and higher-end LSI card that I hadn't used before because
it's PCI-X, and won't fit on my current motherboard.)
I'll report back what I get with it tomorrow or the next day, depending on
the timing on the resilver.
Paul Archer
And the hits just keep coming...
The resilver finished last night, so rebooted the box as I had just
upgraded to the latest Dev build. Not only did the upgrade fail (love that
instant rollback!), but now the zpool won't come online:
r...@shebop:~# zpool import
pool: datapool
id: 3410059226836265661
state: UNAVAIL
status: The pool is formatted using an older on-disk version.
action: The pool cannot be imported due to damaged devices or data.
config:
datapool UNAVAIL insufficient replicas
raidz1 UNAVAIL corrupted data
c7d0 ONLINE
c8d0s0 ONLINE
c9d0s0 ONLINE
c11d0s0 ONLINE
c10d0s0 ONLINE
I've tried renaming /etc/zfs/zpool.cache and rebooting, but no joy.
Is it OK to scream and tear my hair out now?
Paul
PS I don't suppose there's an RFE out there for "give useful data when a
pool is unavailable." Or even better, "allow a pool to be imported (but no
filesystems mounted) so it *can be fixed*."
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
