From owner-freebsd-arm@freebsd.org  Wed Jun 27 02:09:22 2018
Return-Path: <owner-freebsd-arm@freebsd.org>
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 5C5361027E67
 for <freebsd-arm@mailman.ysv.freebsd.org>;
 Wed, 27 Jun 2018 02:09:22 +0000 (UTC)
 (envelope-from marklmi@yahoo.com)
Received: from sonic311-23.consmr.mail.ne1.yahoo.com
 (sonic311-23.consmr.mail.ne1.yahoo.com [66.163.188.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 C92C78E1D8
 for <freebsd-arm@freebsd.org>; Wed, 27 Jun 2018 02:09:21 +0000 (UTC)
 (envelope-from marklmi@yahoo.com)
X-YMail-OSG: dmQxc18VM1kH4nOajh72mAQ5mhr15yHIrL4t0J5pZA09_.NdrL0kl7MKBa21v6S
 pR.4eDwwCHzpm2mz3oC_lYQ7dJwqWx69cU2vDffuGaJPdjMKg4FHoBIiLu0ubGAwrqVaW9MSwKQn
 HdNkgZGYiwGvfgBJV3XubcjtuhlZl3P0iaiCRAkTkqYJfbpPd8AplpRc43f68L5k_Xb5boNg6im3
 YU9JYpufvTjBPCOdxOul5sQC7KarUHKlaAdBzkIu3BRbLKWHBtGEZJvxoo0yhw7Obuw5FEwtoJsJ
 x4k4iJ6Zx5gBgWj8xUUfV6rsUqHL_o4BSkOZTvUtRLcIiRYLDab7I0sbM1mERHfE5K4UDdJV9DWF
 rb9.N9ztrbtmFRv7csOy.dboL.XxHAwVgPHadzMxDqfcvdHPpJSwLFfBAdiVSJkppTtUAM4XO2V6
 YeNAQEuC7WE0vbmzKnCuek7jPGGpb2GBrAlU6e_CKIyzoOSsQhes0cfdkSLKkKSIouLVM.NWHXOt
 rr2nTXhDvoxsnxOZS2FK5Fsi1bojTbokqYXRibdSlqpPuR5iCqJoCnOYBeOqzMnBMkLmLm_uku2H
 1w.W9b7Foo6uH5P0qqcvW4wiCIRBCgrr7j46zymTw.DlVNUOp2jjgLMNXOKeLoCOuVQ4lSFDYaF9
 q0Kn8uI_mNJClj8FoiAvykM.J1HXYvtkmjHbH67OUneauykzImSWZXRO7c8jaScKs2g5ExoTulld
 INuDOk4KoXJJTMIdad8Ti8iozLu.m.JG2nSM02Eji4.fpOeBzENzi1qtk7kpyzfvCifsA6460vfi
 7W6sa8OmAcVvM2D21ZEVoQiPRtihBmt3cbi5tvyzXzUEBwQdvcPCi6mFhvR6QYPnRiTH8elfjr2F
 .H.Lbl2s.whZL8MA.dsOcooMEWFi37P85PzczCkN4kMoKsPDiVvCVezko1J2bkaojPjTQziHwGEC
 fDp12ZVTt6RSzGX.jBYfpoi9wOedOMdrx5A--
Received: from sonic.gate.mail.ne1.yahoo.com by
 sonic311.consmr.mail.ne1.yahoo.com with HTTP; Wed, 27 Jun 2018 02:09:15 +0000
Received: from ip70-189-131-151.lv.lv.cox.net (EHLO [192.168.0.105])
 ([70.189.131.151])
 by smtp401.mail.ne1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID
 0696509309fab90cd916918bf738bac6; 
 Wed, 27 Jun 2018 02:09:10 +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, was Re: GPT vs MBR for swap devices
From: Mark Millard <marklmi@yahoo.com>
In-Reply-To: <20180626222834.GA20270@www.zefox.net>
Date: Tue, 26 Jun 2018 19:09:09 -0700
Cc: Jamie Landeg-Jones <jamie@catflap.org>, Warner Losh <imp@bsdimp.com>,
 freebsd-arm <freebsd-arm@freebsd.org>
Content-Transfer-Encoding: 7bit
Message-Id: <28012DFB-37A0-461A-BB62-CD3EE61E82F0@yahoo.com>
References: <20180623143218.GA6905@www.zefox.net>
 <03C2D3C4-6E90-4054-AF79-BD7FE2B7958D@yahoo.com>
 <20180624231020.GA11132@www.zefox.net>
 <C87C40CF-15B2-4137-892C-F2ADBAB32418@yahoo.com>
 <20180626052451.GA17293@www.zefox.net>
 <CANCZdfpXyzxzOZ8pqcRtuFsxYx5Jjs9oSL1ok2sGVPHdiB0qVQ@mail.gmail.com>
 <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>
To: bob prohaska <fbsd@www.zefox.net>
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." <freebsd-arm.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-arm>,
 <mailto:freebsd-arm-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arm/>
List-Post: <mailto:freebsd-arm@freebsd.org>
List-Help: <mailto:freebsd-arm-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-arm>,
 <mailto:freebsd-arm-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Jun 2018 02:09:22 -0000



On 2018-Jun-26, at 3:28 PM, bob prohaska <fbsd at www.zefox.net> wrote:

> On Tue, Jun 26, 2018 at 01:15:54PM -0700, Mark Millard wrote:
>> On 2018-Jun-26, at 8:18 AM, bob prohaska <fbsd at www.zefox.net> wrote:
>> 
>>> On Tue, Jun 26, 2018 at 07:37:59AM -0700, Mark Millard wrote:
>>>> 
>>>> 
>>>> . . .
>>>> 
>>>> As I remember, Bob P. Did reproduce drive errors even without
>>>> the problem drive being used for swapping. This too suggests
>>>> (A) as separate activity.
>>>> 
>>> Indeed, it is a requirement. If the suspect device is used for swapping
>>> OOMA kills prevent the test from progressing to the point of failure.
>>> 
>> 
>> Looking back at http://www.zefox.net/~fbsd/rpi3/swaptests/
>> and information about /dev/da0 rive errors it does not
>> appear that a combination with:
>> 
>> A) sufficient swap (> 1.5 GiByte total?) but no use of swap on
>>   any partition on /dev/da0
>> and:
>> B) use of /dev/da0 for /usr/ and /var/
>> and:
>> C) Records from the console showing errors (or notes
>>   indicating lack of such errors).
>> 
>> exists. So I was remembering incorrectly.
>> 
>> I'm not claiming such a combination is the best direction for
>> the next tests, but absent such tests there is no
>> compare/contrast to know if /dev/da0 would still get errors
>> despite the system having sufficient swap present on other
>> drives. Thus, I would not go so far as "is a requirement" on
>> the evidence available.
>> 
> 
> I just didn't bother to record successful runs. I'm logging one now.
> 
>> We do have evidence for the system having insufficient swap
>> space: this context seems to have the current status "is
>> sufficient but might not be necessary" for /dev/da0
>> getting drive errors.
>> 
> Not sure I understand here. Basically there seem to be three cases:
> Enough swap not on da0, -j4 buildworld completes.
> Any swap on da0, -j4 buildworld is killed by OOMA
> Not enough swap not on da0, -j4 buildworld crashes the machine eventually.
> 
> Are there other combinations I've overlooked? The first two don't seem 
> worth repeating, at least not often.

"buildworld completes with /dev/da0 errors" vs. "buildworld completes
without /dev/da0 errors" (for: enough swap not on /dev/da0 with no
swap on /dev/da0 ).

That is a little simplistic, as there can be multiple retries
before FreeBSD gives up. Normal is no retries needed. Going
from rare single retries to frequent multiple retries but no
giving-up to it giving up sometimes is all abnormal as I
understand. But there are degrees of abnormal.

And, yes, I have had past examples of significant drive reports
during buildworld that let buildworld appear to complete. (Not
that I trusted the result or the drive involved after such, at
least as the drive was powered/connected at the time.)

For "any swap on da0" and "not enough swap not on da0" (with
no swap on da0) I'd add to your descriptions: "with /dev/da0
errors" (again simplistic).

This goes along with my suggestion to split the /dev/da0
error investigation from the investigations of OMMA behavior
and crashing-the-machine: avoiding any confounding.

(For now I do not have access to a context for doing rpi3
examples myself.)


===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)