tmpfs size option not working

[Jason Schoon]

1.  This isn't a busybox issue.
2.  Is your kernel configured with tmps support, or is it using ramfs
instead?  In 2.6, that option is CONFIG_SHMEM.  Ramfs does not have any size
limiting support.

I use the following line in my fstab on my powerpc embedded system, running
a 2.6 kernel and Busybox:

tmpfs     /tmp    tmpfs    noauto,size=16M,mode=2777    0    0




On 1/4/06, Julien MARBACH <jmarbach at quelisid.com> wrote:
>
> Hello,
> I'm trying to fix the maximum size of a tmpfs (my /var directory) but
> the size=16m option doesn't seem to work. The corresponding line in my
> fstab is :
> none /var        tmpfs   size=16M   0   0
> But if i create a big file under /var I never receive any error message
> telling that the limit has been reached. For example if I do a
>
> $ yes BlahBlahBlah >> /var/test
>
> the file /var/test becomes after a while much larger than the 16MB limit
> I've set and finally uses all the RAM...
>
> I've tried to unmount and remount /var manually after startup with
>
> $ umount /var
> $ mount tmpfs /var -t tmpfs -o size=16m
>
> But the result is the same. The limit is not respected...
>
> Any idea?
>
> Thanks,
>
> julien
> --
> MARBACH Julien
> Embedded software engineer
> Quelis ID Systems
> 11845 Irenee-Vachon
> J7N 1G2 Mirabel (QC)
> Canada
>
> Phone : +1 (450) 476-1930 - x230
> Fax   : +1 (450) 476-0246
>
> --- www.quelisid.com ---
>
>
>
> _______________________________________________
> busybox mailing list
> busybox at busybox.net
> http://busybox.net/cgi-bin/mailman/listinfo/busybox
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.busybox.net/pipermail/busybox/attachments/20060104/cf2ab37a/attachment-0001.htm