Bug#862013: initramfs-tools-core: /run tmpfs size hardcoded at 10% RAM, but 16.0 MiB free required in /run/systemd

2018-05-17 Thread Benjamin Drung
Hi, Using 10% of RAM for /run is a good default, but not suitable for all systems. 10% might be too small for system with less memory (e.g. virtual machine with 160 MiB RAM) or too big (VM host with 256/512 GiB RAM). A too small /run partition leads to not enough space on it. If the /run partition

Bug#862013: initramfs-tools-core: /run tmpfs size hardcoded at 10% RAM, but 16.0 MiB free required in /run/systemd

2017-07-15 Thread José M Cerqueira Esteves
Thanks for the suggestions! On the subject of RAM requirements, for i386 systems (the case in my original message) a minimum of 128 MB is still mentioned in https://www.debian.org/releases/stable/i386/ch03s04.html.en Thus it might make sense to automatically cater for such low-mem i386 systems,

Bug#862013: initramfs-tools-core: /run tmpfs size hardcoded at 10% RAM, but 16.0 MiB free required in /run/systemd

2017-06-26 Thread Russell Coker
On Tuesday, 27 June 2017 4:19:56 AM AEST Michael Biebl wrote: > > Now what can we do about /dev and /sys/fs/cgroup neither of which needs to > > be 24G in size on a system with 48G of RAM? Should I open a new bug > > report about this? > > What exactly would that solve? > Neither of those are wr

Bug#862013: initramfs-tools-core: /run tmpfs size hardcoded at 10% RAM, but 16.0 MiB free required in /run/systemd

2017-06-26 Thread Michael Biebl
Am 27.06.2017 um 04:03 schrieb Russell Coker: > Now what can we do about /dev and /sys/fs/cgroup neither of which needs to be > 24G in size on a system with 48G of RAM? Should I open a new bug report > about > this? What exactly would that solve? Neither of those are writable by the user. Mi

Bug#862013: initramfs-tools-core: /run tmpfs size hardcoded at 10% RAM, but 16.0 MiB free required in /run/systemd

2017-06-26 Thread Russell Coker
For /run specifying the number of inodes is also a good idea. For a system with 160M of RAM it will default to 20480 inodes which may be more than you want on a system with less than the recommended amount of RAM. tmpfs /run tmpfs nosuid,noexec,size=20M,nr_inodes=4096 0 0 The above might be m

Bug#862013: initramfs-tools-core: /run tmpfs size hardcoded at 10% RAM, but 16.0 MiB free required in /run/systemd

2017-06-26 Thread Michael Biebl
Am 27.06.2017 um 02:08 schrieb Michael Biebl: > You can add a entry to /etc/fstab which specifies the desired amount of > RAM for /run. > systemd will remount /run with the size you set very early during boot. > I don't think a separate config option is necessary. Something like this in /etc/fstab

Bug#862013: initramfs-tools-core: /run tmpfs size hardcoded at 10% RAM, but 16.0 MiB free required in /run/systemd

2017-06-26 Thread Michael Biebl
On Sun, 07 May 2017 13:38:11 +0100 J M Cerqueira Esteves wrote: > Package: initramfs-tools-core > Version: 0.130 > Severity: important > > In a virtual machine with 160 MiB RAM, running a freshly installed Debian > stretch system (i686), Since wheezy, the minimum requiremensts are 256M of RAM:

Bug#862013: initramfs-tools-core: /run tmpfs size hardcoded at 10% RAM, but 16.0 MiB free required in /run/systemd

2017-05-07 Thread J M Cerqueira Esteves
Package: initramfs-tools-core Version: 0.130 Severity: important In a virtual machine with 160 MiB RAM, running a freshly installed Debian stretch system (i686), got messages like this logged from (at least) sh and ifup: "Failed to reload daemon: Refusing to reload, not enough space available