Hello,
Anyone else noticed that zpool is kind of negative when reporting back from
some error conditions?
Like:
cannot import 'zpool01': I/O error
Destroy and re-create the pool from
a backup source.
or even worse:
cannot import 'rpool': pool already exists
Destroy and re-create the pool from
a backup source.
The first one i got when doing some failure testing on my new storage node,
i've pulled several disks from a raidz2 to simulate loss off connectivity,
lastly I pulled a third one which as expected made the pool unusable and later
exported the pool. But when I reconnected one of the previous two drives and
tried a import I got this message, the pool was fine once I reconnected the
last disk to "fail", so the messages seems a bit pessimistic.
The second one i got when importing a old rpool with altroot but forgot to
specify a new name for the pool, the solution to just add a new name to the
pool was much better than recreating the pool and restoring from backup.
I think this could scare or even make new users do terrible things, even if the
errors could be fixed. I think I'll file a bug, agree?
Henrik
http://sparcv9.blogspot.com
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
