[zfs-discuss] zfs replace didn't

Roger Bell_West roger at firedrake.org
Wed Jan 6 19:35:37 EST 2016


8-disc raidz2 array, ECC RAM in use. One drive was throwing increasing
numbers of SMART errors (6416 Currently unreadable (pending) sectors),
though not showing up as a problem in zpool status, so I've replaced
it and done

# zpool replace -o ashift=12 storage pci-0000:07:00.0-sas-0x0600000000000000-lun-0

But resilvering threw some errors, and now I have:



# zpool status -v
  pool: storage
 state: DEGRADED
status: One or more devices has experienced an error resulting in data
	corruption.  Applications may be affected.
action: Restore the file in question if possible.  Otherwise restore the
	entire pool from backup.
   see: http://zfsonlinux.org/msg/ZFS-8000-8A
  scan: resilvered 2.71T in 30h31m with 2 errors on Wed Jan  6 17:40:38 2016
config:

	NAME                                                 STATE     READ WRITE CKSUM
	storage                                              DEGRADED     0     0     2
	  raidz2-0                                           DEGRADED     0     0     4
	    pci-0000:07:00.0-sas-0x0000000000000000-lun-0    ONLINE       0     0     0
	    pci-0000:07:00.0-sas-0x0100000000000000-lun-0    ONLINE       0     0     0
	    pci-0000:07:00.0-sas-0x0200000000000000-lun-0    ONLINE       0     0     0
	    pci-0000:07:00.0-sas-0x0300000000000000-lun-0    ONLINE       0     0     0
	    pci-0000:07:00.0-sas-0x0400000000000000-lun-0    ONLINE       0     0     0
	    pci-0000:07:00.0-sas-0x0500000000000000-lun-0    ONLINE       0     0     0
	    replacing-6                                      UNAVAIL      0     0     0
	      10963629787426664018                           UNAVAIL      0     0     0  was /dev/disk/by-path/pci-0000:07:00.0-sas-0x0600000000000000-lun-0-part1/old
	      pci-0000:07:00.0-sas-0x0600000000000000-lun-0  ONLINE       0     0     0
	    pci-0000:07:00.0-sas-0x0700000000000000-lun-0    ONLINE       0     0     0

errors: Permanent errors have been detected in the following files:

        <0x52e>:<0x531f>



So what next? Scrub again? How can the overall pool have checksum
errors when no device on it has had checksum errors?

Roger


More information about the zfs-discuss mailing list