On 04.03.2010, at 02:57, Bob Friesenhahn wrote:
I see lots and lots of zfs traffic on the discussion list "freebsd...@freebsd.org ". This is where the FreeBSD filesystem developers hang out.
Thanks - I'll have a look there. As usual, the cool kids are in mailing lists... ;-)
The zpool status you posted shows that ad16p2 is still in 'replacing' mode. If this is still the case, then it could be a reason that the original disk can't yet be removed.
[...]
If it is still in 'replacing' mode then it seems that the best policy is to just wait. If there is no drive activity on ad4p2 then there may be something more wrong.
It bothers me as well that it says "replacing" instead of replaced or whatever else it should say. Since the resilvering completed I don't have any activity on the drives anymore, so I presume it somehow thinks it's done.
Cold booting a system can be one of the scariest things to do so it should be a means of last resort. Maybe the system would not come back.
That's my fear. Although from what I can gather from the feedback so far the FreeBSD users seem somewhat familiar with an error like that and recommend rebooting. I might take the majority advice, make a backup of the important parts of the pool and just go for a reboot.
Might go for another repost into the freebsd-fs list before, though, so please bear with me that you have to read this again...
Thanks. Christian _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
