[BusyBox] NFS mount problem
bhunt
bhunt at micron.com
Tue Jul 30 13:08:03 UTC 2002
I encountered this using busybox on an embedded system here. The kernel
version that we used was 2.4.18. We found two possible solutions:
* You have to explicitly enable support for NFSV3 in the kernel
configuration in order for busybox mount to use it's default version 3
protocol. (recompile the kernel if you can.) (Option is CONFIG_NFS_V3)
or
* Use the option 'vers=2'. We also use the 'nolock' option. Our command-line
looks like this:
$ mount -t nfs -o nolock,vers=2 somehost:/ /mnt/somedir
HTH,
Brett
> -----Original Message-----
> From: Nicholas Lafferty [mailto:nlafferty at pennswoods.net]
> Sent: Tuesday, July 30, 2002 12:29 PM
> To: busybox at busybox.net
> Subject: [BusyBox] NFS mount problem
>
>
> I'm having trouble getting busybox to mount NFS directories.
> I'm not sure
> what the problem could be.
>
> When i issue:
>
> mount -t nfs -r -o nolock somehost:/ /mnt/somedir
>
> I get the following:
>
> nfs warning: mount version newer than kernel
> NFS: mount program didn't pass remote address!
> mount: Mounting somehost:/ on /mnt/somedir failed: Invalid argument
>
> I can't seem to find the solution anywhere. Has anyone
> encountered this
> before?
>
> Nicholas Lafferty
>
>
> _______________________________________________
> busybox mailing list
> busybox at busybox.net
> http://busybox.net/mailman/listinfo/busybox
>
More information about the busybox
mailing list