Date: Wed, 27 Jun 2018 20:08:01 -0700 From: Mark Millard <marklmi@yahoo.com> To: bob prohaska <fbsd@www.zefox.net> Cc: freebsd-arm@freebsd.org Subject: Re: RPI3 swap experiments Message-ID: <7B9D272D-3EDE-46FA-8A1C-AEE65047167C@yahoo.com> In-Reply-To: <20180628022457.GA30110@www.zefox.net> References: <201806261040.w5QAeBKq035183@donotpassgo.dyslexicfish.net> <A6986B21-FF6E-48F5-9F3A-06B3D2A92C55@yahoo.com> <20180626151843.GD17293@www.zefox.net> <3525D7C7-F848-45A1-BD85-2DAC895DF48C@yahoo.com> <20180626222834.GA20270@www.zefox.net> <28012DFB-37A0-461A-BB62-CD3EE61E82F0@yahoo.com> <20180627054027.GA22144@www.zefox.net> <CC72E766-03CB-476C-8F2B-DAAC266CE63D@yahoo.com> <20180627194217.GA27793@www.zefox.net> <C6303FC5-B412-472C-98E4-9A1E45C38535@yahoo.com> <20180628022457.GA30110@www.zefox.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2018-Jun-27, at 7:24 PM, bob prohaska <fbsd at www.zefox.net> wrote: > On Wed, Jun 27, 2018 at 06:12:53PM -0700, Mark Millard wrote: >> On 2018-Jun-27, at 12:42 PM, bob prohaska <fbsd at www.zefox.net> = wrote: >>=20 >>> On Tue, Jun 26, 2018 at 11:30:52PM -0700, Mark Millard wrote: >>>> . . . >>=20 >>>> For (B), have you tried any examples of: >>>>=20 >>>> insufficient swap on (say) mmcsd0 and no use of the >>>> /dev/da0 drive that has reported errors at all, >>>> /usr/ and /var not on mmcsd0 (or whatever was used >>>> for swap) either? Did some drive end up reporting >>>> errors? Which? Did the system still crash as well? >>>>=20 >>> I think this is the standard test case: >>> /usr and /var on /dev/da0 >>> /tmp on /dev/mmcsd0s3a >>> swap on /dev/mmcsd0s3b >>>=20 >>> This configuration has crashed reliably with errors on /dev/da0 but = no other "disk" errors. >>> Did I understand the question correctly? >>=20 >> I intended for "no use of /dev/da0" to indicate >> that not even /usr or /var were from the device >> that has been logging the errors. For example: >> having /usr or /var on the mechanical disk and >> the known-problem disk not connected at all. >>=20 > Not yet, but absent new developments I'm running out of > other things to try. My hesitations stems partly from my > own sloth, but mostly from a concern that I'll introduce > confounding changes unintentionally. I'm hopeful Jaimie > will get his Pi3 running and see something interesting. >=20 > Some time ago I asked whether it would be better to > dd the existing da0 onto another device or better to > construct a complete new installation (new snapshot > on a new microSD plus a new USB thumb drive). Would > you venture a guess? /dev/da0 is logging write errors. fsck does not correct individual blocks that are part of the content of a file. /dev/da0 is also logging read errors, and, again, fsck does not correct individual blocks that are part of the content of a file. (fsck works on the file system that describes information for finding/using files and their content. [simplistic description]) So I would not trust a copy of /dev/da0 to have avoided the copying already-existing (as read) corruptions of the intended content in various places. =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7B9D272D-3EDE-46FA-8A1C-AEE65047167C>