From owner-freebsd-current@freebsd.org Sun Sep 24 12:19:38 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 05B94E26ED8 for ; Sun, 24 Sep 2017 12:19:38 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7D4FE739E4 for ; Sun, 24 Sep 2017 12:19:36 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([77.179.65.254]) by mail.gmx.com (mrgmx101 [212.227.17.168]) with ESMTPSA (Nemesis) id 0M20Jj-1d6btL1KdH-00tyHo; Sun, 24 Sep 2017 14:19:28 +0200 Date: Sun, 24 Sep 2017 14:19:26 +0200 From: "O. Hartmann" To: Konstantin Belousov Cc: "O. Hartmann" , FreeBSD CURRENT Subject: Re: Dying SD memory? handle_workitem_freefile: got error 5 while accessing filesystem Message-ID: <20170924141926.4c6876dd@thor.intern.walstatt.dynvpn.de> In-Reply-To: <20170924075238.GS2271@kib.kiev.ua> References: <20170924093151.2edfeeff@thor.intern.walstatt.dynvpn.de> <20170924075238.GS2271@kib.kiev.ua> Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/+M_b37R/Yaxce8PLz0ruRLA"; protocol="application/pgp-signature" X-Provags-ID: V03:K0:/O6je/GDDv1K9S0ttmypCnaik7pMsnyFll/kLp7OM/Y7rUxJY1A Q/nDHxJplBRtBrvN7XgPSi9oaWYbo+RkwHOgLtyxuWTKKeHXraBqItrHJ38HZjBUbpm8Ztl h8ZyoO9hxrTMlzRyf44QZkUyDLUgFO5ThbBSkwo7PUN6EVvZCnleh1r7ew6VGET16ITH/mM FvO/t3R0bHkcTtjYmdhJQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:pW+K6/rrBeI=:d3mj+vfpc3tF6eETQQonz7 ZNn4GxIJQ74kRPFZ5D7Y2DXRHr/zJSYWCbquPACd4vlNZXevOcJBQWQvGwrpSOLKS4sYS9bAI lDmqkza8bwmzevmKLv2Ziixa1dw9rSBOTPAQeiubA+8KfbJa6L4L1ZdxmhrT2aacE9YTRx+4X kbARyMDINWaNlajENnZKw9QrGCRpOCQLC6TTLIPJDRlAxZfdSa1DUQzN5GlBbBWWNik4w41Ou jEHBf9WUivhC3rUq2yAGTUjAnQHlmi7uJlsigITuwa9higFNPuS57l7Bozo45gyoR6CzbY7ca xNBNqu9/cjp2P+5hww2LhC//y8sZOd4EGHNwDp8r06RTEUSB4fUt0ZBTPKLNRoGWs6eBR6Y08 1I14C9num46VzkCBOtzQcwkWrYmqBqEPlDL5EnLplNg474FcOhCSYIq1/Xh7L/tN3CMtVsdqP sskhmarhifJR2qMx/L/BmB8ZVgUmXiUagVBx9DFwz0cxRiHuv4nlFsHWpw6DZpf5sLmUnYk7m R4sWy+4l+mdH64E40O1xzScCxHIkJJ8N8KroKj1SxthKJG+dnXeZXBjHfKBE5vO81cTxg/W5S Xr1eSVgGsYnn24+j9cuRSaAojsIqfpipjzTIQc5RclmBLLOElt+Ik9INCPZEE/WXQ1+wZ2jlA IhLqovvF6//YbijNRu1gBfhMxn4jIti44Dd0fB9LNwpOJqHKtlLcw6LMv3KP02PyyomaDFXvM +pmmplMi65a95zf4XJhV6cK1PelH/kg/T9DxuRKjGeeMftVJCLl5pQaVcJXwvrTWpQd9JaWbN 3UDGqpvPwEtbgYfqBx7sDF0H3MxTw== X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Sep 2017 12:19:38 -0000 --Sig_/+M_b37R/Yaxce8PLz0ruRLA Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Am Sun, 24 Sep 2017 10:52:38 +0300 Konstantin Belousov schrieb: > On Sun, Sep 24, 2017 at 09:31:51AM +0200, O. Hartmann wrote: > > Running a NanoBSD application on a small PCEngine device, feeding the b= ox with a > > CURRENT (FreeBSD 12.0-CURRENT #33 r323958: Sat Sep 23 22:19:57 CEST 201= 7 amd64), > > booting from a SD memory card. > >=20 > > Recently, when saving configuration changes on the SD memory card, I re= ceive these > > strange errors: > >=20 > > [...] > > checksum failed: cg 0, cgp: 0xb478d1d5 !=3D bp: 0x874608df > > checksum failed: cg 12, cgp: 0xe626d67c !=3D bp: 0x7360c12a > > checksum failed: cg 0, cgp: 0xb478d1d5 !=3D bp: 0x874608df > > handle_workitem_freefile: got error 5 while accessing filesystem > > checksum failed: cg 12, cgp: 0xe626d67c !=3D bp: 0x7360c12a > > handle_workitem_freefile: got error 5 while accessing filesystem > > [...] > >=20 > > I do not use MMCCAM in the kernel, but as far as I know, the problem oc= cured in the > > same time frame.=20 > >=20 > > The question is: is the SD memory about to die and is to be replaced or= is this a bug > > introduced with the new MMCCAM stuff recently? =20 >=20 > The messages you see about 'checksum_failed' are due to recently added > UFS feature where cylinder group blocks are checksummed, and the checksum > is verified against the known one stored on the volume. >=20 > Were there kernel messages about disk I/O errors before that (as opposed > to UFS errors about checksums and SU complains) ? Hello, no, there were no errors before. The small box is updated on a frequent bas= is, so I'm sure there were no errors like those before or any other kind regarding I/O. I recall having read the commit description about the UFS2 enhancement. The NanoBSD image is created using UFS2/GPT partitioning scheme, if this is= important to know.=20 Regards, Oliver --=20 O. Hartmann Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3=BCr Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 28 Abs.= 4 BDSG). --Sig_/+M_b37R/Yaxce8PLz0ruRLA Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWceizgAKCRDS528fyFhY lP64Af9yUue8ZFcTHwOw02USilSKJAsYMG53lxiHviJAImBgyzXOeREiL8+5/ebg cSVV7cXwea5WUOrO52u/uzBQrhLeAf0fXrRY0HADNssh2m7tAUyZ/+h8997o1u4+ NnlGXQ+sEJvqCZmty/YTRNtFEmD8HE6X5nAJTktKpuXtWsrjHTnc =pXx6 -----END PGP SIGNATURE----- --Sig_/+M_b37R/Yaxce8PLz0ruRLA--