• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 98 subscribers
  • Views 500 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

NFS client on ICS

Alireza Kenarsari Anhari
Intellectual 500 points

Hi,

I am trying to setup a build environment for OMAP blaze device which is running ice cream sandwich. I am trying to mount a folder from my Linux box (Ubuntu) to blaze using NFS. After setting up the server on Ubuntu I use the following command on omap to map the drive:

mount -t nfs IP_OF_UBUNTU_MACHINE:/SOME_DIR/ /sdcard/nfs/SOME_DIR_2

which returns with the following error message: "invalid argument". I already checked the following: (1) IP is correct as I can ping it (2) source and destination directories exist (3) after doing "make menconfig" in kernel's directory I noted that "NFS client support" is actually selected. Could anybody help me resolve this issue?

Thanks,

Alireza

  • 0
    TI__Genius 10545 points

    By typing "man mount" in terminal the option nfs3 is not available try using nfs or nfs4;

    Mount options for nfs and nfs4
           See the options section of the nfs(5) man page (nfs-common package must be installed).

    A point to check is next link

    http://omapedia.org/wiki/Android_enabling_codecs#To_enable_with_external_access_point

    and adding some options to command line it could depend on how PC's NFS is configured
           defaults
                  Use default options: rw, suid, dev, exec, auto, nouser, and async.

  • 0 in reply to Manuel Contreras
    Intellectual 500 points

    Yes I noted that and updated the post accordingly. Now I am using

    mount -t nfs ...

    which returns "invalid argument". On a side note. Please correct me if I am wrong. The "mount" utility on android is not the same as the linux one. i.e. "man mount" does not necessarily give me correct information. e.g. typing "mount --version " returns error on android.

  • 0 in reply to Alireza Kenarsari Anhari
    TI__Genius 10545 points

    Right;

    I  just ran mount -t nfs4 and "invalid argument" error became "no such device" i used my PC's IP address that is not using a nfs server.

    try using nfs4

    source code for mount is in toolbox code, it has menu options

    ./27.IS.2/mydroid/system/core/toolbox/mount.c

  • 0 in reply to Manuel Contreras
    Intellectual 500 points

    Thanks a lot for double checking. Yes using nfs4 returns "No such device" for me too. But this I would expect as nfs4 is not built as a part of ice cream sandwich release (i.e. default configuration of kernel excludes it). Still wondering how this could go wrong as I am pretty sure a lot of OMAP developers should rely on it for driver/software development. Hopefully someone would have an answer :)

  • 0 in reply to Alireza Kenarsari Anhari
    Guru 26430 points

    Your version of mount might not support NFS. See Xavier's post here:

    http://e2e.ti.com/support/dsp/davinci_digital_media_processors/f/717/p/143416/517672.aspx#517672

    Check to see which mount program you are using by "which mount" on the target. You might be running "/bin/mount" or a symbolic link to "/bin/busybox".

  • 0 in reply to Norman Wong
    TI__Genius 10545 points

    one link for Busybox in Android is

    http://omapedia.org/wiki/Android_Installing_Busybox_Command_Line_Tools