On Wed, 23 Sep 2009, Dustin Marquess wrote:
Okay.. I "fixed" it by powering the server off, removing the new drive, letting
the pool come up degraded, and then doing zpool replace.
I'm assuming what happened was ZFS saw that the disk was online,
tried to use it, and then noticed that the checksums didn't match
(of course) and marked the pool as corrupted. The question is why
didn't ZFS check the labels on the drive and see that the drive
wasn't in the pool and kick it out itself?
You never told us what OS and version (OpenSolaris, Solaris 10,
FreeBSD, NetBSD, Linux Fuse, OS X zfs preview) you are using. If you
are using an older version of zfs, maybe a newer version works as
expected?
Never report a problem without identifying the software and hardware
you are using.
Bob
--
Bob Friesenhahn
bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer, http://www.GraphicsMagick.org/
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
