From: Jon Ringle <jon@ringle.org>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] systemctl daemon-reload fails
Date: Wed, 28 Oct 2020 09:27:35 -0400 [thread overview]
Message-ID: <CAMwGMjywQOob_BNUK+VMFV4a0fjv0uUzihxiFCHn3Xg81oEPNg@mail.gmail.com> (raw)
In-Reply-To: <20201028073733.GF3084@pengutronix.de>
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
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
-Jon
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
next prev parent reply other threads:[~2020-10-28 13:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-19 18:32 Jon Ringle
2020-10-19 18:36 ` Jon Ringle
2020-10-20 6:04 ` Ladislav Michl
2020-10-20 12:57 ` Jon Ringle
2020-10-21 7:27 ` Ladislav Michl
2020-10-28 7:28 ` Michael Olbrich
2020-10-28 7:37 ` Michael Olbrich
2020-10-28 13:27 ` Jon Ringle [this message]
2020-10-28 17:40 ` Michael Olbrich
2020-10-29 7:13 ` Alexander Dahl
2020-10-29 8:05 ` Michael Olbrich
2020-10-29 8:33 ` Alexander Dahl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAMwGMjywQOob_BNUK+VMFV4a0fjv0uUzihxiFCHn3Xg81oEPNg@mail.gmail.com \
--to=jon@ringle.org \
--cc=ptxdist@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox