From owner-freebsd-current@freebsd.org Sun Sep 24 12:44:42 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 5652CE27A24 for ; Sun, 24 Sep 2017 12:44:42 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id F2CE374913 for ; Sun, 24 Sep 2017 12:44:41 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id v8OCiaYV088786 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 24 Sep 2017 15:44:36 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua v8OCiaYV088786 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id v8OCia7U088785; Sun, 24 Sep 2017 15:44:36 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Sun, 24 Sep 2017 15:44:36 +0300 From: Konstantin Belousov To: "O. Hartmann" Cc: FreeBSD CURRENT Subject: Re: Dying SD memory? handle_workitem_freefile: got error 5 while accessing filesystem Message-ID: <20170924124436.GU2271@kib.kiev.ua> References: <20170924093151.2edfeeff@thor.intern.walstatt.dynvpn.de> <20170924075238.GS2271@kib.kiev.ua> <20170924141926.4c6876dd@thor.intern.walstatt.dynvpn.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170924141926.4c6876dd@thor.intern.walstatt.dynvpn.de> User-Agent: Mutt/1.9.0 (2017-09-02) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home 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:44:42 -0000 On Sun, Sep 24, 2017 at 02:19:26PM +0200, O. Hartmann wrote: > 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 box with a > > > CURRENT (FreeBSD 12.0-CURRENT #33 r323958: Sat Sep 23 22:19:57 CEST 2017 amd64), > > > booting from a SD memory card. > > > > > > Recently, when saving configuration changes on the SD memory card, I receive these > > > strange errors: > > > > > > [...] > > > checksum failed: cg 0, cgp: 0xb478d1d5 != bp: 0x874608df > > > checksum failed: cg 12, cgp: 0xe626d67c != bp: 0x7360c12a > > > checksum failed: cg 0, cgp: 0xb478d1d5 != bp: 0x874608df > > > handle_workitem_freefile: got error 5 while accessing filesystem > > > checksum failed: cg 12, cgp: 0xe626d67c != bp: 0x7360c12a > > > handle_workitem_freefile: got error 5 while accessing filesystem > > > [...] > > > > > > I do not use MMCCAM in the kernel, but as far as I know, the problem occured in the > > > same time frame. > > > > > > 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? > > > > 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. > > > > 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 basis, 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. Try to read the SD card on pre-checksum kernel. If you can read it, verify that the files are not damaged. This is a way to check whether your SD card or controller provides the wrong data to host.