hi, --- replacing UNAVAIL 0 543 0 insufficient replicas ------ 17096229131581286394 FAULTED 0 581 0 was /dev/dsk/c0t2d0s0/old ------ 11342560969745958696 FAULTED [u][b]0 582 0[/b][/u] was /dev/dsk/c0t2d0s0
Looking at that, i dont think you have fixed the original fault. Its still getting write errors. Thats why the resilvering has stopped i recon. There there any spare drive connection's on the system? Could you free up a drive connection? So you can plug the drive in to a different connection. You will need to resolve the hardware error, is it the drive, the cable or hard drive controller. Remember a hard drives best trick is to "act alive and well" when is really at deaths door..... One of ZFS's best features is its ability to sniff out hardware faults. To restart the resilver, do a zpool clear and zpool online. This will force the zpool and the hard drive online. It will start to resilver, do a zpool status -v to monitor the process. Watch out for the error count on the drive. Dont do this till you really think you have got the error fixed. How is your back up situation? Get you critical data off the zpool before attempting to repair the zpool or change any thing with the zpool. What i would do is, get a new drive, connect it to a different hard drive connection and use a new cable. Remove the old drive, unplug it. I would not try to replace the faulty drive while is still connected, things are just going to get confusing. Your zpool status will then show the drive as missing. Zpool replace with the new drive. Your zpool with be fixed in a few hours. Your zpool may give errors across other drives, as long as its <50 just use zpool clear. your hardware fault my have been causing trouble for ages without you knowing. Am an amateur ZFS er so use my advice with caution. Brian, -- This message posted from opensolaris.org _______________________________________________ zfs-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
