Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 18 Feb 2018 03:38:49 +0000
From:      tech-lists <tech-lists@zyxst.net>
To:        bob prohaska <fbsd@www.zefox.net>
Cc:        freebsd-arm@freebsd.org
Subject:   Re: Pi3 out of swap at < 50%
Message-ID:  <3d2bd5e3-4567-cdfe-04d4-b572371a212e@zyxst.net>
In-Reply-To: <20180218003840.GD93736@www.zefox.net>
References:  <20180217162732.GA93736@www.zefox.net> <1518885801.91697.2.camel@freebsd.org> <9bf0ca6e-1916-3f4d-71fe-0515fe6a717f@zyxst.net> <20180218003840.GD93736@www.zefox.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On 18/02/2018 00:38, bob prohaska wrote:
> The arm64 RPI3 also has 2 GB configured in two equal partitions, one 
> on the USB flash drive and one on the microSD card used for booting. 
> It's claiming "out of swap" with only about 50% usage. Swapinfo shows
> both partitions are being used, so that's not the problem. Kernel and
> world are a couple weeks out of sync, which might be a problem but it
> can't be checked until buildworld runs to completion, which it hasn't. 

In that situation I'd deactivate the swap on the card, and make a few
swap partitions on the flash drive. I used to run into the sort of
difficulty you're seeing if swap was on the microsd. It's not just swap
though; enough i/o activity on the card and it starts blocking. You can
tell it's happening if in another terminal if you type sync. It takes
several seconds (sometimes tens of seconds) to return.

I'd like to be able to set async on the connected HD but it seems even
when it's set in fstab it doesn't show up when the mount command is
issued. The HD connects via a powered hub btw.

These days I don't do updates or compiling on the rpi3 itself now that
poudriere/synth can cross-compile ports. If I need to update the OS I'll
use crochet to build an image from whatever sources on a beefy amd64
then restore my data. I must have gone through dozens of microsd cards
before arriving at this solution. Some just completely fail, others
suddenly become read-only.

There's probably a solution in dd'ing the card image to a more powerful
computer, mounting the image and crossbuilding into it which would be
more efficient I think but I haven't tried it yet.
-- 
J.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3d2bd5e3-4567-cdfe-04d4-b572371a212e>