mount bug [was: Re: tmpfs]

Jason Schoon floydpink at gmail.com
Sun Aug 20 18:32:03 UTC 2006


On 8/20/06, Chey <chey.smith at gmail.com> wrote:
>
> On 8/20/06, Jason Schoon <floydpink at gmail.com> wrote:
> > On 8/20/06, Bernhard Fischer <rep.nop at aon.at> wrote:
> >
> > > On Sun, Aug 20, 2006 at 09:38:54AM -0400, Chey wrote:
> > > >Is anyone else having this problem?
> > >
> > > This is likely a generic bug in the new mount and should go away if
> you
> > > revert to the mount from version 1.0+fixes-but-no-rewrites .
> > >
> > > Rob may already have a fix for this pending, though.
> > > HTH,
> >
> >
> > I have this in use on my system currently, with Busybox 1.2.1 and it
> works
> > correctly.  What kernel version is this where you are seeing the error?
> >  Specifically, you need to make sure that CONFIG_TINY_SHMEM is not
> enabled
> > in your kernel.  If it is, your tmpfs is actually being implemented by
> > ramfs, which does not support size constraints.
> >
>
> I have tried with CONFIG_TINY_SHMEM enabled and disabled and still
> have the same problem. Another thing I would like to mention is that
> when I send the "mode=xxx" option to mount it doesn't pass that
> either. For example:
>
> mount tmpfs /tmp -t tmpfs -o size=4264k,nosuid,nodev,mode=1777
>
> Maybe mount isn't happy with options that have an equal sign? I
> haven't fully tested for that though.
>
> I haven't been able to revert mount to version
> 1.0+fixes-but-no-rewrites for testing yet.


I am using it and have it working correctly with:
mount -t tmpfs -o size=4M,mode=2777 tmpfs /tmp

Maybe it is either the nosuid or nodev that are causing it problems?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.busybox.net/pipermail/busybox/attachments/20060820/135b8652/attachment.htm 


More information about the busybox mailing list