Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 28 Dec 2016 11:42:53 -0400
From:      Joseph Mingrone <jrm@ftfl.ca>
To:        freebsd-fs@freebsd.org
Cc:        Dmitry Marakasov <amdmi3@amdmi3.ru>, Steven Hartland <killing@multiplay.co.uk>
Subject:   Re: ZFS resilver from disk with bad sectors constantly restarts
Message-ID:  <86zijgf4aq.fsf@ftfl.ca>
In-Reply-To: <20151030103614.GL57666@hades.panopticon> (Dmitry Marakasov's message of "Fri, 30 Oct 2015 13:36:14 %2B0300")
References:  <20151030103614.GL57666@hades.panopticon>

next in thread | previous in thread | raw e-mail | index | archive | help
--=-=-=
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

Dmitry Marakasov <amdmi3@amdmi3.ru> writes:
> I've just got a case where resilvering a new replacement disk in raidz2
> never finished.

> The problem: one disk in raidz is failing by having a large number of
> unreadable sectors. It's replaced with a spare. Resilver though is
> constantly restarted with log full of read error from bad disk.=20

> It looks like this:

> ---
>   pool: spool
>  state: ONLINE
> status: One or more devices is currently being resilvered.  The pool will
> 	continue to function, possibly in a degraded state.
> action: Wait for the resilver to complete.
>   scan: resilver in progress since Wed Oct 28 05:26:28 2015
>         369G scanned out of 9,87T at 123M/s, 22h29m to go
>         41,4G resilvered, 3,65% done
> config:

> 	NAME                  STATE     READ WRITE CKSUM
> 	spool                 ONLINE       0     0     0
> 	  raidz1-0            ONLINE       0     0     0
> 	    ada0              ONLINE       0     0     0
> 	    ada1              ONLINE       0     0     0
> 	    spare-2           ONLINE       0     0   733
> 	      ada11           ONLINE       0     0     0
> 	      ada2            ONLINE       0     0     0  (resilvering)
> 	  raidz1-1            ONLINE       0     0     0
> 	    ada3              ONLINE       0     0     0
> 	    ada4              ONLINE       0     0     0
> 	    ada5              ONLINE       0     0     0
> 	  raidz1-2            ONLINE       0     0     0
> 	    ada6              ONLINE       0     0     0
> 	    ada7              ONLINE       0     0     0
> 	    ada10             ONLINE       0     0     0
> 	spares
> 	  588540573008830286  INUSE     was /dev/ada2

> errors: No known data errors
> ---

> `resilver in progress since' date is constantly reset, so resilved
> progress cannot pass beyond 5% or so. My guess is that it happens on
> read errors on ada11. I think I've seen (resilvering) on ada11 line
> couple of times.

> In the end I've had to offline ada11 and after that resilver completed
> in under 16 hours. However the situation doesn't seem normal, as I'd
> prefer to not lose redundancy with offlining dying disk and still be
> able to use it for resilvering (imagine there were bad sectors on ada0/1
> as well, but not intersecting with bad sectors on ada11), or at least
> some more verbose indication of why the resilver is constantly restarted.

> I should also note that's outdated FreeBSD 9.1, so maybe that problem
> was fixed already.

We have been dealing with, what seems to be, the same issue on 11.0-RELEASE=
 with
a two-raidz1-vdev pool.  You said that your issue was with a raidz2, but yo=
ur
zpool status output shows raidz1.  The problem disk had checksum mismatches=
 and
smart was reporting errors, but it was still online.  The resilver would ma=
ke it
through many hours, but then restart.  This loop went on for a few days.  A=
s in
your case, after offlining the problem disk, the replacement finished.

--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQJ8BAEBCgBmBQJYY919XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ1NUIwOTNBNzI2QzM4ODU1NzEyMkJBRDUz
NkE0MEM4M0IwRDZFRjlFAAoJEDakDIOw1u+eBWEQAJVFWKPF9qvJTBvbt0JSsKw7
tgFYsa/EMD59rJpyIW+ASpfLczgDBgrGZCm2LCQadbqjnCgjKhDv6/Uo4kviRoaq
Xg7AWOsYAQ09B3aS9zDDySaBDu4oDFCCQFiWYqzh5xm9kVnhVvCPKTywFbFmiLq0
8WZa9fvD7pYpDFMgFLxM83Z/MWclN2Cyk+SX9g87hezcc2Sr6XRXpw2S+w/KdUIr
kw1ZmuDh3nqNObjgkYAqxcNc0XLEr6J4HPEKKK76HXDp/WrQ7H0peE9NmkDYQd4W
2HUKE6xPXQQDYDCQCr5Ywg4N/VJovcOQXx7ulD2SxVzj6oRUu+8suMFubOA69dGN
yNgpgqiRYOxXpsUzX8PDUglNRySLQ2ysh+NcVwQyYxfho19DtTbM0VLiFEIMkaBH
qqk/0lkyr5vTRo2c/6ybghkjJsHzpP51v69120fdhR+h9UrunCo4dcjmLz4kgV6f
KedkJpsxYmp7W5sC4t3QKRAy7UqQJBwzbPBOH/JVhUM2airlYxyW1VJAmMm2lQIT
n8y+6oV9Ue1fuykNCQo2DC9wr2ZyVfft8DO8cuXEDdyDlWQjVmXS5x470RDY6laE
0uNHCOr2z2j6fsPqTrb3iFMuObdIxF3KZXngEVbCpe9KCenZg5PWzm/+zd7vHSuW
vN/lTRHj9U3idaR6C9xo
=YFhG
-----END PGP SIGNATURE-----
--=-=-=--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86zijgf4aq.fsf>