From owner-freebsd-arm@freebsd.org Thu Jun 28 03:08:09 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 919D9102FF9E for ; Thu, 28 Jun 2018 03:08:09 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic311-23.consmr.mail.gq1.yahoo.com (sonic311-23.consmr.mail.gq1.yahoo.com [98.137.65.204]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 16AA384123 for ; Thu, 28 Jun 2018 03:08:08 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: D_T6fRgVM1nH.E91HmZIeNQ33X67CYIgtr57JUfUJ2kKCDxWHyT5vaoEboV62CY REgfI.MdrZlqHSw0pfRz.ZG9BO4iGjB_y0pYh3LPR5XuucvkTprguWTp9fylh6q7BVdIaj7D1JM1 FFvwNHPrYsL0C5pwQ7hikxldFEAgd7GInTYkkLiOpog3SbXcP1qIL.JTHiEL8vEfiKozuPcFG2dq 9jM0RNSa2Ti.egIVuqSciUij_WiMBhVZKok.2C3JuVTVeUxFgiAeF66OpLTJOh3g01wvHdrwWhCk NG2gwNDzB2bqk6wvqW_YX_AxcV7mJBUfpF_WAni.jTlpKhrhsv1rDekLALVkqWvYGylC5wGU9k0T op86ENz_Q3JXFxKvLJzYQDJFbq3HQLBdkR2IuZB2wjQ9OjSFe1lCsEFVBsxvTzgWz8lDddbpEVEp weH2IyKXWjwjZFYtYUErJACN_ByBg6zRsAO9godNNPrpfO7qmmXLppuVI8wajS2THxkbbEyC9QH7 fpv2blsqAMrEHuSokCTm6yBRp8HnMK88sSs4.SEQ4rOyoKuA0lGHJCEvnds3eQc9pukZE5YoSFlH EYA0HCWG_lAv2glQfTL9ph_w_bhoo35NH9VsdmFWwEVZmxyjaX7z9k5uDtcVvzl4uZG339yC8vls Vpufo7ct_lS_bxrYPQfOF9PXn1ezFMNkfI1Tb_I.0WyyuxpeT.Q1P69Sk3HfP6Xy3ZaovVLyYmTJ QnCXsCde2sBaGkve7zKCIDAWqbSZDKepnxuDH06gJ5u_OsnV3gWajSIek84KJ6s22G6gcG8w_J4t AcQr4t8e2WTdAGRUzFjeP5T2BOd2Ol6Em5b6KGmne_XqVSjOPcKksN0htHSvPpLRYmb4O3GQLUOZ w1u3ngpggL1v0lEKDwJf5_YJxvYsJjLoQ9G8Ptv879AD541OVZgRMHztjAlYugvEb4AesFjzlHq6 idRYQcM8SjK1QQLc5C.UltepWhSgC Received: from sonic.gate.mail.ne1.yahoo.com by sonic311.consmr.mail.gq1.yahoo.com with HTTP; Thu, 28 Jun 2018 03:08:07 +0000 Received: from ip70-189-131-151.lv.lv.cox.net (EHLO [192.168.0.105]) ([70.189.131.151]) by smtp409.mail.gq1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 4ed461f45197dd995d84f5e28745961b; Thu, 28 Jun 2018 03:08:03 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\)) Subject: Re: RPI3 swap experiments From: Mark Millard In-Reply-To: <20180628022457.GA30110@www.zefox.net> Date: Wed, 27 Jun 2018 20:08:01 -0700 Cc: freebsd-arm@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <7B9D272D-3EDE-46FA-8A1C-AEE65047167C@yahoo.com> References: <201806261040.w5QAeBKq035183@donotpassgo.dyslexicfish.net> <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> <20180627194217.GA27793@www.zefox.net> <20180628022457.GA30110@www.zefox.net> To: bob prohaska X-Mailer: Apple Mail (2.3445.8.2) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Jun 2018 03:08:09 -0000 On 2018-Jun-27, at 7:24 PM, bob prohaska wrote: > On Wed, Jun 27, 2018 at 06:12:53PM -0700, Mark Millard wrote: >> On 2018-Jun-27, at 12:42 PM, bob prohaska = 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)