Re: Dying SD memory? handle_workitem_freefile: got error 5 while accessing filesystem

> 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_at_freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"
> 

-- 
Rod Grimes                                                 rgrimes_at_freebsd.org