From owner-freebsd-current@freebsd.org Sun Sep 24 07:52:44 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 5D4C1E21F16 for ; Sun, 24 Sep 2017 07:52:44 +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 E8E2F6D7C9 for ; Sun, 24 Sep 2017 07:52:43 +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 v8O7qces025092 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 24 Sep 2017 10:52:39 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua v8O7qces025092 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id v8O7qcER025091; Sun, 24 Sep 2017 10:52:38 +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 10:52:38 +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: <20170924075238.GS2271@kib.kiev.ua> References: <20170924093151.2edfeeff@thor.intern.walstatt.dynvpn.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170924093151.2edfeeff@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 07:52:44 -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 > [...] > > 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) ?