From owner-freebsd-current@freebsd.org Sun Sep 24 15:33:01 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 7E4FCE2A242 for ; Sun, 24 Sep 2017 15:33:01 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 490FE7CF1B for ; Sun, 24 Sep 2017 15:33:00 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1]) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id v8OFWsvR008080; Sun, 24 Sep 2017 08:32:54 -0700 (PDT) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: (from freebsd-rwg@localhost) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id v8OFWsWN008079; Sun, 24 Sep 2017 08:32:54 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201709241532.v8OFWsWN008079@pdx.rh.CN85.dnsmgr.net> Subject: Re: Dying SD memory? handle_workitem_freefile: got error 5 while accessing filesystem In-Reply-To: <20170924075238.GS2271@kib.kiev.ua> To: Konstantin Belousov Date: Sun, 24 Sep 2017 08:32:54 -0700 (PDT) CC: "O. Hartmann" , FreeBSD CURRENT X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Mailman-Approved-At: Mon, 25 Sep 2017 04:13:17 +0000 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 15:33:01 -0000 > 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 > > [...] Would it be possible to add some robustness to these checksum failed errors to indicate there source more accurately? Ie either a /dev entry or a fstab entry, and the fact they are from the ffs layer? > > 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) ? > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > -- Rod Grimes rgrimes@freebsd.org