Date: Tue, 8 Nov 2022 17:28:00 +0800 From: Archimedes Gaviola <archimedes.gaviola@gmail.com> To: mike@karels.net Cc: freebsd-arm@freebsd.org, jmg@freebsd.org Subject: Re: adding swap when expanding root filesystem Message-ID: <CAJFbk7EeKyVNzYNhmKuYh2ZzzgoHRcZ0eUPNxii-6vyyGZg-aA@mail.gmail.com> In-Reply-To: <202211071610.2A7GAcHl090048@mail.karels.net> References: <202211071610.2A7GAcHl090048@mail.karels.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--00000000000087735b05ecf229a8 Content-Type: text/plain; charset="UTF-8" On Tue, Nov 8, 2022 at 12:10 AM Mike Karels <mike@karels.net> wrote: > This question is not really arm-specific, but I couldn't think of a better > mailing list for it. > > There are peridic issues reported on small systems like Raspberry Pi > where people are running buildworld or poudriere and running out of > memory. As the user gets no control over the disk layout when installing, > there is no option to add swap space on the install image. I have added > swap space on a USB disk, but this is often not an option. It occurred > to me that it might be reasonable to add swap space before expanding > the root filesystem if there is sufficient space. I have a prototype, > and wondered if this is a good thing to do. Granted, this will often > create swap on microSD, which is not optimal, but probably better than > nothing. > > The current prototype creates a swap partition which is 1/10 of the disk > if the disk is at least 15 GB and the initial root partition is no more > than 1/3 of the disk, but only up to 1.5x of physical memory. I would > probably enable this by default, but provide a way to disable it via a > kenv variable and/or a variable in /etc/rc.conf. > > Thoughts? > > Mike > Hi Mike, That's a pleasant to have as my current scenario belongs to this concern using RPi 3B/4B as build machines. Thanks and best regards, Archimedes --00000000000087735b05ecf229a8 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">= <div dir=3D"ltr" class=3D"gmail_attr">On Tue, Nov 8, 2022 at 12:10 AM Mike = Karels <<a href=3D"mailto:mike@karels.net">mike@karels.net</a>> wrote= :<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.= 8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">This question = is not really arm-specific, but I couldn't think of a better<br> mailing list for it.<br> <br> There are peridic issues reported on small systems like Raspberry Pi<br> where people are running buildworld or poudriere and running out of<br> memory.=C2=A0 As the user gets no control over the disk layout when install= ing,<br> there is no option to add swap space on the install image.=C2=A0 I have add= ed<br> swap space on a USB disk, but this is often not an option.=C2=A0 It occurre= d<br> to me that it might be reasonable to add swap space before expanding<br> the root filesystem if there is sufficient space.=C2=A0 I have a prototype,= <br> and wondered if this is a good thing to do.=C2=A0 Granted, this will often<= br> create swap on microSD, which is not optimal, but probably better than<br> nothing.<br> <br> The current prototype creates a swap partition which is 1/10 of the disk<br= > if the disk is at least 15 GB and the initial root partition is no more<br> than 1/3 of the disk, but only up to 1.5x of physical memory.=C2=A0 I would= <br> probably enable this by default, but provide a way to disable it via a<br> kenv variable and/or a variable in /etc/rc.conf.<br> <br> Thoughts?<br> <br> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Mike<br></blockquot= e><div><br></div><div>Hi Mike,</div><div><br></div><div>That's a pleasa= nt to have as my current scenario belongs to this concern using RPi 3B/4B a= s build machines.</div><div><br></div><div>Thanks and best regards,</div><d= iv>Archimedes <br></div></div></div> --00000000000087735b05ecf229a8--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJFbk7EeKyVNzYNhmKuYh2ZzzgoHRcZ0eUPNxii-6vyyGZg-aA>