Re: [ptxdist] systemctl daemon-reload fails

[Alexander Dahl <ada@thorsis.com>]

Hei hei,

Am Mittwoch, 28. Oktober 2020, 18:40:58 CET schrieb Michael Olbrich:
> On Wed, Oct 28, 2020 at 09:27:35AM -0400, Jon Ringle wrote:
> > On Wed, Oct 28, 2020 at 3:59 AM Michael Olbrich
> > 
> > <m.olbrich@pengutronix.de> wrote:
> > > On Wed, Oct 28, 2020 at 08:28:11AM +0100, Michael Olbrich wrote:
> > > > On Wed, Oct 21, 2020 at 09:27:54AM +0200, Ladislav Michl wrote:
> > > > > On Tue, Oct 20, 2020 at 08:57:27AM -0400, Jon Ringle wrote:
> > > > > > On Tue, Oct 20, 2020 at 2:06 AM Ladislav Michl <ladis@linux-
mips.org> wrote:
> > > > > > > On Mon, Oct 19, 2020 at 02:32:49PM -0400, Jon Ringle wrote:
> > > > > > > > I recently updated to ptxdist-2020.10.0 for running on our
> > > > > > > > device that
> > > > > > > > has 64MB or physical ram.
> > > > > > > > With systemd-246.6 that is installed,I'm finding that systemd
> > > > > > > > daemon-reload now fails:
> > > > > > > > 
> > > > > > > > $ sudo systemctl daemon-reload
> > > > > > > > Failed to reload daemon: Refusing to reload, not enough space
> > > > > > > > available on /run/systemd. Currently, 10.6M are free, but a
> > > > > > > > safety
> > > > > > > > buffer of 16.0M is enforced.
> > > 
> > > Out of curiosity: What is filling up /run for you? I've always had
> > > plenty
> > > of space in /run.
> > 
> > On my target, it only has 64M of DRAM. After the kernel has reserved
> > its memory, only 55.5M is available for user space. It seems that /run
> 
> Huh, I haven't used a system with less than 256M of SDRAM in a long time.
> I'm living in a different filter bubble... :-)

For the record: we still work with boards designed ten years ago with 32 MiB 
RAM and run almost recent ptxdist and LTS kernel. I assume systemd + 
additional dependencies (udev, dbus, …) would make those completly unusable.

Our new boards have 128 MiB though.

> 
> > is implicitly using a size=20% that is defined for /tmp in fstab:
> > $ grep tmpfs /etc/fstab
> > tmpfs   /tmp                    tmpfs
> > nosuid,nodev,mode=1777,size=20%         0 0
> > tmpfs   /run                    tmpfs
> > nosuid,nodev,strictatime,mode=0755      0 0
> > tmpfs   /var/lock               tmpfs
> > nosuid,nodev,noexec,mode=0755,size=1M   0 0
> > tmpfs   /var/tmp                tmpfs
> > nosuid,nodev,mode=1777,size=20%         0 0
> > $ df -h|grep tmpfs
> > devtmpfs                  4.0M         0      4.0M   0% /dev
> > tmpfs                    27.7M         0     27.7M   0% /dev/shm
> > tmpfs                    11.1M    464.0K     10.6M   4% /run
> > tmpfs                     4.0M         0      4.0M   0% /sys/fs/cgroup
> > tmpfs                    11.1M      2.9M      8.1M  27% /tmp
> > tmpfs                     1.0M         0      1.0M   0% /var/lock
> > tmpfs                    11.1M         0     11.1M   0% /var/tmp
> > 
> > So, to begin with, /run with a size of 11.1M is already too small even
> > if completely unused to meet the criteria imposed by systemctl
> > daemon-reload
> 
> I thinks that's worth a bug report for systemd. I'm not sure if someone
> will actually do something about it, unless you write the patch yourself.
> At least it reminds people that systemd is used on embedded systems with
> very little resources.

If someone creates such a report, please let me know.

A




_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de