Date: Tue, 1 Feb 2022 08:18:08 -0800 From: bob prohaska <fbsd@www.zefox.net> To: freebsd-arm@freebsd.org Cc: bob prohaska <fbsd@www.zefox.net> Subject: Error detection for microSD-based swap, buildworld failures on pi3 Message-ID: <20220201161808.GA73977@www.zefox.net> In-Reply-To: <14716537-6E22-44F5-B6AA-841E3EB2AD04@yahoo.com> References: <20220129022255.GA59340@www.zefox.net> <6B822440-6F01-4578-803C-20A51DADF10C@yahoo.com> <20220130020546.GA63792@www.zefox.net> <1964F2B7-EC41-42C8-9C18-5E2B79EE0271@yahoo.com> <F4CAC6F9-B9E8-4BD3-BFA0-1706BE56A2AD@yahoo.com> <5B3DF910-23B1-4246-999E-0196E90269F2@yahoo.com> <20220131165333.GA69543@www.zefox.net> <9E0510D2-9FAC-4F01-89A3-E6D8C7C21FDA@yahoo.com> <20220131221405.GA70251@www.zefox.net> <14716537-6E22-44F5-B6AA-841E3EB2AD04@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[new subject, different emphasis, old problem] On Mon, Jan 31, 2022 at 03:06:01PM -0800, Mark Millard wrote: > > One thing that could fit the behavior is if small part(s) > of the system c++ compiler (or libraires it uses) were > corrupted on that specific media. In that case, nothing > elsewhere would replicate the failures but a lot might > work without using the corrupted part(s), making the > failures not random. [spaced for emphasis] > Checking on that is part of why > I'd hoped to get a lldb report for a .sh/.cpp pair > leading to failure on your RPi3* in question. > If/when the stable/13 Pi3 finishes its -j1 single-user build/install cycle I'll make a point of trying the .sh/.cpp test under lldb. For most of their operational history both troublesome Pi3 systems have had some of their swap on microSD. If there is no error detection at all for microSD-based storage then undetected corruption of data from swap is a real possibility. I expected that storage errors would be reported but maybe not, especially outside file systems. Mechanical disks have some internal error detection and report explictly when data can't be retrieved. As I think back on it at least one flash device (a USB thumb drive) failed silently, no reported errors but also no-write. That was on a filesystem, so the OS noticed and so did I. Is there any error detection/correction employed by the virtual memory system as it reads and writes mass storage? Thanks for reading!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20220201161808.GA73977>