Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 11 Jun 2023 19:06:45 +0100
From:      Graham Perrin <grahamperrin@freebsd.org>
To:        Alexander Motin <mavbsd@gmail.com>, freebsd-fs@freebsd.org
Cc:        FreeBSD CURRENT <freebsd-current@freebsd.org>
Subject:   Re: Following a panic (271945): zpool status reports 1 data error but identifies no file
Message-ID:  <9180ef68-2729-c9e7-907f-74c7e9e6204b@freebsd.org>
In-Reply-To: <93e6e7e6-f877-be39-a6d3-ac17564b535a@gmail.com>
References:  <64407335-27be-ca28-68e3-3d3b39afc5a5@freebsd.org> <93e6e7e6-f877-be39-a6d3-ac17564b535a@gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--------------fDn70Vpd0U07xekR0ykmGztW
Content-Type: multipart/mixed; boundary="------------ao98Zp3VJggLHAQajVh6Vqpk";
 protected-headers="v1"
From: Graham Perrin <grahamperrin@freebsd.org>
To: Alexander Motin <mavbsd@gmail.com>, freebsd-fs@freebsd.org
Cc: FreeBSD CURRENT <freebsd-current@freebsd.org>
Message-ID: <9180ef68-2729-c9e7-907f-74c7e9e6204b@freebsd.org>
Subject: Re: Following a panic (271945): zpool status reports 1 data error but
 identifies no file
References: <64407335-27be-ca28-68e3-3d3b39afc5a5@freebsd.org>
 <93e6e7e6-f877-be39-a6d3-ac17564b535a@gmail.com>
In-Reply-To: <93e6e7e6-f877-be39-a6d3-ac17564b535a@gmail.com>

--------------ao98Zp3VJggLHAQajVh6Vqpk
Content-Type: multipart/alternative;
 boundary="------------h3bLeo5u3NrsKk1tq76KtzOU"

--------------h3bLeo5u3NrsKk1tq76KtzOU
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: base64

T24gMTEvMDYvMjAyMyAxNDo0OCwgQWxleGFuZGVyIE1vdGluIHdyb3RlOg0KPiBPbiAxMS4w
Ni4yMDIzIDA4OjAyLCBHcmFoYW0gUGVycmluIHdyb3RlOg0KPj4gU2VlIGJlbG93LCBzaG91
bGQgSSBiZWdpbiBzY3J1YmJpbmc/IE9yIChiZWZvcmUgSSBiZWdpbikgbWlnaHQgemRiIA0K
Pj4gcmV2ZWFsIHNvbWV0aGluZyB1c2VmdWw/DQo+DQo+IFRoZSBvbmx5IGNhc2Ugd2hlbiBJ
IHdvdWxkIG5vdCByZWNvbW1lbmQgdG8gcnVuIHNjcnViIGlzIGlmIHRoZXJlIGlzIGEgDQo+
IHN1c3BpY2lvbiBvZiBtZW1vcnkgY29ycnVwdGlvbnMgb24gdGhlIHN5c3RlbSAoaGFyZHdh
cmUgb3Igc29mdHdhcmUpLCANCj4gbGlrZSBhIGJhZCBSQU0sIGluIHdoaWNoIGNhc2Ugc2Ny
dWIgbWF5ICJmaW5kIiBlcnJvcnMgdGhhdCBhcmUgbm90IA0KPiB0aGVyZSwgdHJhc2hpbmcg
dGhlIHBvb2wgZXZlbiBtb3JlLsKgIE90aGVyd2lzZSBpdCBqdXN0IHZlcmlmaWVzIA0KPiBj
aGVja3N1bXMsIHRyeWluZyB0byBmaW5kIHZhbGlkIGRhdGEgY29waWVzIGFuZCB1cGRhdGUg
d2hhdCBpcyANCj4gYWZmZWN0ZWQuIEl0IGlzIG5vdCBhbiBmc2NrLCBpdCBkb2VzIG5vdCBj
aGFuZ2UgdGhpbmdzIGFyYml0cmFyaWx5Lg0KDQpUaGFua3MuIE5vIHN1c3BlY3RlZCBtZW1v
cnkgY29ycnVwdGlvbiBpbiB0aGlzIGNhc2UuDQoNCkkgY2hvc2UgdG8gYmVnaW4gc2NydWJi
aW5nIGEgZmV3IGhvdXJzIGFnby4gSSB0aGluayBpdCBsaWtlbHkgdGhhdCB0aGUgDQpyZXBv
cnRlZGx5IHBlcm1hbmVudCBlcnJvciB3aWxsIHNpbXBseSBkaXNhcHBlYXIgd2hlbiB0aGUg
c2NydWIgY29tcGxldGVzLg0KDQp6ZGIg4oCmIG1pZ2h0IGJlIGxvb2tpbmcgZm9yIGEgbmVl
ZGxlIGluIGEgaGF5c3RhY2ssIHdoZW4gdGhlcmUncyB6ZXJvIA0KaW5mb3JtYXRpb24gYWJv
dXQgd2hhdCBkYXRhIGlzIGFmZmVjdGVkIGJ5IHRoZSBvbmUgZGF0YSBlcnJvci4NCg0K
--------------h3bLeo5u3NrsKk1tq76KtzOU
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<html data-lt-installed=3D"true">
  <head>
    <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DUTF=
-8">
  </head>
  <body style=3D"padding-bottom: 1px;">
    <div class=3D"moz-cite-prefix">On 11/06/2023 14:48, Alexander Motin
      wrote:<br>
    </div>
    <blockquote type=3D"cite"
      cite=3D"mid:93e6e7e6-f877-be39-a6d3-ac17564b535a@gmail.com">On
      11.06.2023 08:02, Graham Perrin wrote:
      <br>
      <blockquote type=3D"cite">See below, should I begin scrubbing? Or
        (before I begin) might zdb reveal something useful?
        <br>
      </blockquote>
      <br>
      The only case when I would not recommend to run scrub is if there
      is a suspicion of memory corruptions on the system (hardware or
      software), like a bad RAM, in which case scrub may "find" errors
      that are not there, trashing the pool even more.=C2=A0 Otherwise it=

      just verifies checksums, trying to find valid data copies and
      update what is affected. It is not an fsck, it does not change
      things arbitrarily.
      <br>
    </blockquote>
    <p>Thanks. No suspected memory corruption in this case. <br>
    </p>
    <p>I chose to begin scrubbing a few hours ago. I think it likely
      that the reportedly permanent error will simply disappear when the
      scrub completes.=C2=A0</p>
    <p>zdb =E2=80=A6 might be looking for a needle in a haystack, when th=
ere's
      zero information about what data is affected by the one data
      error. <br>
    </p>
  </body>
  <lt-container></lt-container>
</html>

--------------h3bLeo5u3NrsKk1tq76KtzOU--

--------------ao98Zp3VJggLHAQajVh6Vqpk--

--------------fDn70Vpd0U07xekR0ykmGztW
Content-Type: application/pgp-signature; name="OpenPGP_signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="OpenPGP_signature"

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

wsF5BAABCAAjFiEEWT/lssMHB+28ly8Kt2dIb0oY1AsFAmSGDTYFAwAAAAAACgkQt2dIb0oY1AtK
+g//Ug3J82k1av5YTbb0IifgmlCr/1iyhR0SZyEQoOaOZa7/+uy5q++1SjWENVJqt4pvCKXIV1Tc
4jPIAEuVkpUUnNMSyNYwZ7O5onvZd+UAqlC2u9H+2MG+I+pcuvnKldXOexozkXd+EkH4m5ApuUSu
psZAqxVpzzbQlunFqnE7cy+UpzQrScs+RHg+52QW4pGVQWbJPXL43NjyImVZtrdrKC2LQhr8/bPr
Zr7LhYREh4q7Uoq2tti1vul4HNAGk6gwPbgWuxaOaxMMzoKK9zfiTA0WUYOwFBOBfQwQtcBDKrFP
VvSzmOURFFjOlOuVPWOi6YSlD7VuRH2GwBW8yjblx69WwVneSeQEp8S6OINJHdZePgre1daQt8KV
/XqQx38kRXhaJ39aoXKkFoCzEfGksEoH9lVDAVCDnuC7CGBZAbIcRa6Zl6G4kJsGKZCODSDqBfoI
CaSQwIu+weICxB/S1wjVVQyGLNtuL0QBvTd1w/JjJvfaXHFb4GH9mAlbzk8JIMst8n5lFPPlfzjq
BCV6Zc0PNrToRehA8ZGorELat45Jo5eE2UosQmQTzwitglokpAwUHzLHYnLCdw18sm99Q8EA8Vz5
DyLs3F111YJVswifWjYrS8UcHGnzgiPDEnY5V7BLsF1PnLKY7LHTz6S8Cmdy4fGruAU0H1rpCfOe
PO8=
=UI0n
-----END PGP SIGNATURE-----

--------------fDn70Vpd0U07xekR0ykmGztW--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9180ef68-2729-c9e7-907f-74c7e9e6204b>