[BusyBox] mount problems

[rich_wilson at agilent.com]

This sounds familiar:

I had a problem with mount which I tracked down to an interaction
between an unlucky memory page alignment, and a PPC kernel bug (2.4.14).
The fix for me was to add a long phony "-o" option to force the
memory alignment to change.  So, my startup script has 
  mount -t proc -o mounthasaproblem none /proc
instead of
  mount -t proc none /proc
because the latter would fail.  I think the failure indication
was "Bad address"

I believe that the problem could also be worked around by
fiddling with variable allocation within busybox.

I reported the problem to my contact at MontaVista, but I have no
idea whether it went anywhere from there.  I'll look up my explanation
of the problem if anyone is interested.

Rich

Rich Wilson
Agilent Technologies
425-335-2245
rich_wilson at agilent.com

> -----Original Message-----
> From: Brendan J Simon [mailto:brendan.simon at ctam.com.au]
> Sent: Monday, July 15, 2002 11:22 PM
> To: busybox at busybox.net
> Subject: [BusyBox] mount problems
> 
> 
> I'm using busybox.0.60.2 with a powerpc linux.2.4.18-pre8 
> kernel.  I'm 
> having troubles with the mount command.
> 
> I have a startup script that does a "mount -a".  All the 
> mounts seem to 
> fail.
>     mount: Mounting proc on /proc failed: Bad address
>     mount: Mounting tmpfs on /tmp failed: No such device
>     mount: Mounting tmpfs on /var/log failed: No such device
> Note that "mount -t proc proc /proc" works fine if run 
> manually at the 
> shell prompt.
>     # mount /proc
>     #
> 
> I am also trying to mount tmpfs but getting errors.  If I 
> type "mount -t 
> tmpfs tmpfs /tmp" I get a "Bad address" error.  It seems to 
> work OK if I 
> add a "-o mode=700" option.  ie. "mount -t tmpfs tmpfs /tmp 
> -o mode=700" 
> works fine.
>     # mount -t tmpfs tmpfs /tmp
>     mount: Mounting tmpfs on /tmp failed: Bad address
>     # mount -t tmpfs tmpfs /tmp -o mode=700
>     #
> 
> Any clues as to what's going on ?  I'm running the kernel and root 
> filesystem from an NFS server for development purposes.  
> Could this be 
> causing problems ???
> 
> My /etc/fstab is:
>     #/dev/nftla1         /        ext2   
> ro,suid,dev,exec,async,noatime  0 1
>     #/dev/nftla2         /var     ext2   
> rw,suid,dev,exec,async,noatime  0 2
>     #/dev/nftla1         /        ext2   defaults    0 1
>     #/dev/nftla2         /var     ext2   defaults    0 2
>     proc                /proc    proc   defaults    0 0
>     tmpfs               /tmp     ramfs  defaults    0 0
>     tmpfs               /var/log ramfs  defaults    0 0
>     #ramfs               /tmp     ramfs  defaults    0 0
>     #ramfs               /var/log ramfs  defaults    0 0
>     192.168.0.5:/home   /home    nfs    rw,defaults,nolock 0 0
> 
> Thanks for any help or pointers.
> Brendan Simon.
> 
> 
> _______________________________________________
> busybox mailing list
> busybox at busybox.net
> http://busybox.net/mailman/listinfo/busybox
>