On Dec 28, 2009, at 2:01 PM, Morten-Christian Bernson wrote:
I tried changing cables, nothing changed. Then I saw something
about smartmontools on the net, and I installed that. It reported
that c2t4d0 had indeed reported a SMART error. Why didn't Solaris
detect this?
In your OP, I see:
c2t4d0 Soft Errors: 153
I then went ahead and offlined c2t4d0, after which the pool
performed much more like expected with excellent speeds.
good!
I tried to do a zpool replace with the hotspare, but it was
connected through another raid controller which seems to have taken
some of the sectors to itself, which lead to the disk being too
small to be able to replace the defective, even though they are
identical... This was a good thing to discover before it was too
late as well :)
In later builds, a few sectors here or there will be accommodated.
I then physically replaced the defective drive with the hotspare,
and then the resilvering could begin. If everything goes well,
maybe it will be in normal working condition again in the morning :)
Thanks to everyone for helping out.
Good luck!
-- richard
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
