Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 14 Aug 2022 10:21:26 -0700
From:      Mark Millard <marklmi@yahoo.com>
To:        Nuno Teixeira <eduardo@freebsd.org>
Cc:        FreeBSD Mailing List <freebsd-ports@freebsd.org>
Subject:   Re: Resolved: devel/llvm13 build: "ninja: build stopped: subcommand failed"
Message-ID:  <21FC1F5E-240E-4A8C-A5D2-6B73494026C0@yahoo.com>
In-Reply-To: <CAFDf7UJmBNvfVo3SAenPUk1WkFgvpkqoM6=Riv6pwaovuNnAWg@mail.gmail.com>
References:  <1D4C14BD-8955-4B86-9C99-3E58D7603122.ref@yahoo.com> <1D4C14BD-8955-4B86-9C99-3E58D7603122@yahoo.com> <CAFDf7UK-pAFXCrZZA9veASaa-wf9HKMdX52fxmcmDgRFiNOF7A@mail.gmail.com> <7CDC63F3-8B68-420E-8012-B1692667E293@yahoo.com> <CAFDf7UJmBNvfVo3SAenPUk1WkFgvpkqoM6=Riv6pwaovuNnAWg@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 2022-Aug-14, at 10:15, Nuno Teixeira <eduardo@freebsd.org> wrote:

> I use ZFS.
>=20
> I will follow your recomendations and use a swap of 64GB and then test =
it again.
>=20
> In the meanwhile I will take a look at freebsd docs to see how do I =
increase swap, by adding a new swap file or resize actual one if =
possible.

I recommend never using a swap file, only swap partition(s), in order
to avoid deadlocks and such:

On 2017-Feb-13, at 7:20 PM, Konstantin Belousov <kostikbel at gmail.com> =
wrote
on the freebsd-arm list:

. . .

swapfile write requires the write request to come through the filesystem
write path, which might require the filesystem to allocate more memory
and read some data. E.g. it is known that any ZFS write request
allocates memory, and that write request on large UFS file might require
allocating and reading an indirect block buffer to find the block number
of the written block, if the indirect block was not yet read.

As result, swapfile swapping is more prone to the trivial and =
unavoidable
deadlocks where the pagedaemon thread, which produces free memory, needs
more free memory to make a progress.  Swap write on the raw partition =
over
simple partitioning scheme directly over HBA are usually safe, while =
e.g.
zfs over geli over umass is the worst construction.



=3D=3D=3D
Mark Millard
marklmi at yahoo.com




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?21FC1F5E-240E-4A8C-A5D2-6B73494026C0>