From: glphvgacs <darwinskernel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: cap on rootfs
Date: Thu, 6 Mar 2014 14:34:42 -0500 [thread overview]
Message-ID: <20140306193442.GA498@localhost> (raw)
hello,
so after reading
Documentation/filesystems/ramfs-rootfs-initramfs.txt
and
Documentation/filesystems/tmpfs.txt
i thought i would put everything in /* into initrd since i have 8G of
ram sitting around with pretty much no use. crazy? maybe.
but i must have hit an old cap on how much one can shove into initramfs
which is not cool, IMHO. here are related sizes:
$ ls -lh /boot/initramfs.cpio.gz:
1.2G Mar 5 16:59 /boot/initramfs.cpio.gz
$ df -h:
Filesystem Size Used Avail Use% Mounted on
rootfs 3.3G 3.3G 0 100% /
devtmpfs 3.4G 0 3.4G 0% /dev
note that df -h on rootfs is not even consistent; last boot i had 2.8G!
in both cases it violates what Documentations say, which is 50% of the
availabe ram.
now services can't write to for example /var/tmp/ since we're out of
space. remounting / will *fix* it:
# mount -o remount,size=90% /
$ df -h:
Filesystem Size Used Avail Use% Mounted on
rootfs 7.0G 3.3G 3.8G 47% /
but that's no solution.
so my question:
where is this set in kernel? is there a kernel param i can pass to
kernel to give it the go ahead to use 90% of the availabe ram? i have
btw tried rootflags=size=90% thinking that it might work like it does in
fstab for tmpfs, no luck. or is there a CONFIG_* that sets this? i
didn't try messing with CONFIG_BLK_DEV_RAM_SIZE since that seemed to be
for ramdisk and in any case too small to be the one being used, in my
case:
CONFIG_BLK_DEV_RAM_SIZE=4096
kernel version btw:
3.14.0-rc5 #1 SMP PREEMPT x86_64 Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz
thanks
next reply other threads:[~2014-03-06 19:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-06 19:34 glphvgacs [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-03-12 17:03 cap on rootfs glphvgacs
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=20140306193442.GA498@localhost \
--to=darwinskernel-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.