From nobody Sun Aug 14 18:07:33 2022 X-Original-To: freebsd-ports@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4M5QPF3tp7z4YYKN for ; Sun, 14 Aug 2022 18:07:45 +0000 (UTC) (envelope-from eduardo@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4M5QPF3SLXz45gB for ; Sun, 14 Aug 2022 18:07:45 +0000 (UTC) (envelope-from eduardo@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1660500465; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=R8MH+FeMxxMRtgitZL95OAq11FpWEuLjLd30RcWg7B8=; b=UOfHBwkO3+Loh/s2VUeMs0KdQquaK1dIqDAnL1+/2LGy6pewNjlm11ItOG0yZMiPhLzbkC gvcrfHPrJKt49xcUHIRUMrClJTTcIURCtdFFm+u3YEiq82PBaHvoaV/htnKWQ9El9FHFET 7pxM42S+1bMuqZHIoVCPwJMjf4oB0C33iYjnqyJmvfeP70VYSFGKvXbgyUzggdlyOuRHQC hPgmwTcqlR0Lac2cnh4LOmFtnvizrEj0qsmHrx+k/yxuvjFWu1PTFV/3+aBeyaxkMl+oo0 70XSsVDHvXkMempZDHSoj9xlK+nCCPkt+3H4Oq5UFCYaFsGUMQ840ujk8dY5kQ== Received: from mail-vk1-f178.google.com (mail-vk1-f178.google.com [209.85.221.178]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) (Authenticated sender: eduardo) by smtp.freebsd.org (Postfix) with ESMTPSA id 4M5QPF2Pfzz1DSx for ; Sun, 14 Aug 2022 18:07:45 +0000 (UTC) (envelope-from eduardo@freebsd.org) Received: by mail-vk1-f178.google.com with SMTP id j11so2793488vkk.11 for ; Sun, 14 Aug 2022 11:07:45 -0700 (PDT) X-Gm-Message-State: ACgBeo1gQGgIQIe6oatJJBtAmvQ//x46M6EkR5oIKupDRIgU4j06WDwy icdwlR4vDFRZOiJPqmNpTuJUEYJGpabr9QW95/c= X-Google-Smtp-Source: AA6agR6IjAAxzo0QwX0/B8v0ibM4Pi9bZWH9jRoBTpk1jJLG4KqFw2254ZuGlvCwLoFQg/PbTnmJr7YHMewIwGMdkQA= X-Received: by 2002:a1f:41c8:0:b0:377:1352:8f9d with SMTP id o191-20020a1f41c8000000b0037713528f9dmr5120389vka.25.1660500464745; Sun, 14 Aug 2022 11:07:44 -0700 (PDT) List-Id: Porting software to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-ports List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org MIME-Version: 1.0 References: <1D4C14BD-8955-4B86-9C99-3E58D7603122.ref@yahoo.com> <1D4C14BD-8955-4B86-9C99-3E58D7603122@yahoo.com> <7CDC63F3-8B68-420E-8012-B1692667E293@yahoo.com> <21FC1F5E-240E-4A8C-A5D2-6B73494026C0@yahoo.com> <3E3F8980-8214-45E9-9530-D78243A29D41@yahoo.com> In-Reply-To: <3E3F8980-8214-45E9-9530-D78243A29D41@yahoo.com> From: Nuno Teixeira Date: Sun, 14 Aug 2022 19:07:33 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Resolved: devel/llvm13 build: "ninja: build stopped: subcommand failed" To: Mark Millard Cc: FreeBSD Mailing List Content-Type: multipart/alternative; boundary="00000000000059ca1a05e6376417" ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1660500465; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=R8MH+FeMxxMRtgitZL95OAq11FpWEuLjLd30RcWg7B8=; b=w3eZW+rzRB+wRz4VWhm+y8jvCxEVg5HyFcDwEz1Yd/ciyt0136Bumyj+mV1EKoKvQOSQno bHB+EJrjTTh6mukRwjucYQsdb5BeWxRc9VQ8gJNK5XfUtO+rNuBLwHxY1e6JSTeomhNSX7 tFAq7SgtleIBZO3FcYsaDgjeRI44UtnAkSdotefwDfIExjYURIsxQCoi8rPEuJVTVido3K 6y62BRlKMnZ0qXGbIqQoVJazi7zJg1oe+J9BuhbuIFfz8nONFvQFSXDdk5onhbGZYwnlqV frd0Mw4S/206kbbiErWrUGWFK2N+u9UzouyX+U8DU/7UIq4fjy8dVn/9Br/RRg== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1660500465; a=rsa-sha256; cv=none; b=bSZxRej2uHxI9vd8ijO/AX0LVCj+v9y8A90d19wciX8E3HWT3ZyoAsgD8FblqAZhANnmN4 vXk2GSsta3M8JmUgw5mH72/LxTL/YxyuIK6y+OOE7jk8tVkdOVLBNf3OO23KxNZUCgnPaa Q7ZOnlPOw5bBRv8fwUYlRUPmkHMhigxknqXUgBZwTIdAmKgUZSvuKJrZbGUGWX9LCCS1Cq XPe23eBF8l9ossDJSO3MPsT4AnYFW1v8cWnDS+/7JNbisz5th1zzejv1Y5Y5wduRgBrZir b47aPXFg8GjsH0143nEtnHUDorbB/4/+9iYaVe2eCHGJ2ejHtuJhseRhEhZjCQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N --00000000000059ca1a05e6376417 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I will follow https://docs.freebsd.org/en/books/handbook/book/#disks-growin= g and resize actual swap, but before that I will have to make sure that backups are ok in case of something goes wrong. I've tooked a note about total swap <=3D60GB Thanks Mark Millard escreveu no dia domingo, 14/08/2022 =C3=A0= (s) 18:46: > > On 2022-Aug-14, at 10:31, Nuno Teixeira wrote: > > > > Ok, I will avoid a swap file. > > > > My actual config shows: > > `swapinfo`: > > --- > > Device 1K-blocks Used Avail Capacity > > /dev/nvd0p2 4194304 6036 4188268 0% > > --- > > and `cat /etc/fstab`: > > --- > > # Device Mountpoint FStype Options Dump > Pass# > > /dev/nvd0p1 /boot/efi msdosfs rw 2 = 2 > > /dev/nvd0p2 none swap sw 0 0 > > --- > > > > Any clues how do I do this? > > You can have more than one swap partition active, such that > the total is the size that you want. (I do this to have > various freebsd-swap partition sizes available for media > that can be used to boot multiple systems with widely > varying amounts of RAM: sometimes having, say, 3 partitions > in use to get a desired total, for example.) > > So you could even plug in a new device and create a > freebsd-swap type partition on it to add, say, 56 GiBytes > of SWAP to what you already have. > > I've no clue about your other media that you might be > able to use, partitioning on media, etc. and so can not > be very specific for your context. > > > Mark Millard escreveu no dia domingo, 14/08/2022 > =C3=A0(s) 18:21: > > On 2022-Aug-14, at 10:15, Nuno Teixeira wrote: > > > > > I use ZFS. > > > > > > I will follow your recomendations and use a swap of 64GB and then tes= t > it again. > > Note that I recommended up to 60 GB total SWAP, not 64 GB total > SWAP. 64 GB total would produce warnings about potential > mistuning for a 16 GiByte RAM machine. I avoid such > configurations. > > > > 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 > wrote > > on the freebsd-arm list: > > > > . . . > > > > swapfile write requires the write request to come through the filesyste= m > > 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 requir= e > > allocating and reading an indirect block buffer to find the block numbe= r > > of the written block, if the indirect block was not yet read. > > > > As result, swapfile swapping is more prone to the trivial and unavoidab= le > > deadlocks where the pagedaemon thread, which produces free memory, need= s > > 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 > > --=20 Nuno Teixeira FreeBSD Committer (ports) --00000000000059ca1a05e6376417 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I will follow https://docs.freebsd.org/en/books/handb= ook/book/#disks-growing and resize actual swap, but before that I will = have to make sure that backups are ok in case of something goes wrong.

I've tooked a note about total swap <=3D60GB

Thanks

Mark Millard <marklmi@yahoo.com> escreveu no dia domingo, 14/08/= 2022 =C3=A0(s) 18:46:
> On 2022-Aug-14, at 10:31, Nuno Teixeira <eduardo@freebsd.org> wrote:
>
> Ok, I will avoid a swap file.
>
> My actual config shows:
> `swapinfo`:
> ---
> Device=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 1K-blocks=C2=A0 =C2=A0 =C2=A0= Used=C2=A0 =C2=A0 Avail Capacity
> /dev/nvd0p2=C2=A0 =C2=A0 =C2=A0 =C2=A04194304=C2=A0 =C2=A0 =C2=A06036= =C2=A0 4188268=C2=A0 =C2=A0 =C2=A00%
> ---
> and `cat /etc/fstab`:
> ---
> # Device=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Mountp= oint=C2=A0 =C2=A0 =C2=A0 FStype=C2=A0 Options=C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0Dump=C2=A0 =C2=A0 Pass#
> /dev/nvd0p1=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0/boot/efi= =C2=A0 =C2=A0 =C2=A0 =C2=A0msdosfs rw=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 2=C2=A0 =C2=A0 =C2=A0 =C2=A02
> /dev/nvd0p2=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0none=C2=A0 = =C2=A0 swap=C2=A0 =C2=A0 sw=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0= 0=C2=A0 =C2=A0 =C2=A0 =C2=A00
> ---
>
> Any clues how do I do this?

You can have more than one swap partition active, such that
the total is the size that you want. (I do this to have
various freebsd-swap partition sizes available for media
that can be used to boot multiple systems with widely
varying amounts of RAM: sometimes having, say, 3 partitions
in use to get a desired total, for example.)

So you could even plug in a new device and create a
freebsd-swap type partition on it to add, say, 56 GiBytes
of SWAP to what you already have.

I've no clue about your other media that you might be
able to use, partitioning on media, etc. and so can not
be very specific for your context.

> Mark Millard <marklmi@yahoo.com> escreveu no dia domingo, 14/08/2022 =C3=A0(s) 1= 8:21:
> On 2022-Aug-14, at 10:15, Nuno Teixeira <eduardo@freebsd.org> wrote:
>
> > I use ZFS.
> >
> > I will follow your recomendations and use a swap of 64GB and then= test it again.

Note that I recommended up to 60 GB total SWAP, not 64 GB total
SWAP. 64 GB total would produce warnings about potential
mistuning for a 16 GiByte RAM machine. I avoid such
configurations.

> > 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 possibl= e.
>
> I recommend never using a swap file, only swap partition(s), in order<= br> > to avoid deadlocks and such:
>
> On 2017-Feb-13, at 7:20 PM, Konstantin Belousov <kostikbel at gmail.com&= gt; wrote
> on the freebsd-arm list:
>
> . . .
>
> swapfile write requires the write request to come through the filesyst= em
> 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 requi= re
> allocating and reading an indirect block buffer to find the block numb= er
> of the written block, if the indirect block was not yet read.
>
> As result, swapfile swapping is more prone to the trivial and unavoida= ble
> deadlocks where the pagedaemon thread, which produces free memory, nee= ds
> more free memory to make a progress.=C2=A0 Swap write on the raw parti= tion 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



--
Nun= o Teixeira
FreeBSD Committer (ports)
--00000000000059ca1a05e6376417--