[QtMoko] Problem mounting a nfs directory

[NeilBrown]

On Wed, 29 Jan 2014 18:26:11 +0100 Giacomo 'giotti' Mariani
<giacomomariani at yahoo.it> wrote:

> On 01/29/2014 06:02 PM, Giacomo 'giotti' Mariani wrote:
> > Hello everyone,
> >     in order to compile something on my freerunner I'd like to use for
> > that a nfs directory+chroot.
> >
> > I edited fstab accordingly and tried to mount:
> >
> > root at neo:/mnt/nfs# mount `pwd`
> > mount: wrong fs type, bad option, bad superblock on
> > 192.168.0.200:/home/jack/Programmazione/Openmoko/Distros/QtMoko/CHROOT/,
> >        missing codepage or helper program, or other error
> >        (for several filesystems (e.g. nfs, cifs) you might
> >        need a /sbin/mount.<type> helper program)
> >        In some cases useful info is found in syslog - try
> >        dmesg | tail  or so
> >
> > Consequently I tried to install nfs-common, but:
> >
> > root at neo:/mnt/nfs# apt-get install nfs-common
> > Reading package lists... Done
> > Building dependency tree       
> > Reading state information... Done
> > The following NEW packages will be installed:
> >   nfs-common
> > 0 upgraded, 1 newly installed, 0 to remove and 2 not upgraded.
> > Need to get 0 B/180 kB of archives.
> > After this operation, 623 kB of additional disk space will be used.
> > Selecting previously unselected package nfs-common.
> > (Reading database ... 12006 files and directories currently installed.)
> > Unpacking nfs-common (from .../nfs-common_1%3a1.2.6-4em1_armel.deb) ...
> > Setting up nfs-common (1:1.2.6-4em1) ...
> >
> > Creating config file /etc/idmapd.conf with new version
> >
> > Creating config file /etc/default/nfs-common with new version
> > [FAIL] Starting NFS common utilities: statd idmapd failed!
> > invoke-rc.d: initscript nfs-common, action "start" failed.
> > dpkg: error processing nfs-common (--configure):
> >  subprocess installed post-installation script returned error exit status 1
> > Errors were encountered while processing:
> >  nfs-common
> > E: Sub-process /usr/bin/dpkg returned an error code (1)
> >
> >
> > I googled and tried some stuff like "apt-get install portmap" or
> > "apt-get install -f", but with no results.
> > Do you have any suggestion?
> >
> > Thanks a lot,
> >   Giacomo
> >
> I've to correct myself, sorry.
> 
> If I do:
> 
> root at neo:/mnt/nfs# mount.nfs
> 192.168.0.200:/home/jack/Programmazione/Openmoko/Distros/QtMoko/CHROOT/
> /mnt/nfs/
> 
> It mounts "well":
> 
> root at neo:/mnt/nfs# mount
> [...]
> 192.168.0.200:/home/jack/Programmazione/Openmoko/Distros/QtMoko/CHROOT
> on /mnt/nfs type nfs4
> (rw,relatime,vers=4,rsize=524288,wsize=524288,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.0.202,minorversion=0,local_lock=none,addr=192.168.0.200)
> 
> But there is something that does not seem to work as I expect: even if
> /home/jack/Programmazione/Openmoko/Distros/QtMoko/CHROOT it's not empty:
> 
> root at neo:/mnt/nfs# ls
> root at neo:/mnt/nfs#
> 
> and, viceversa, if I create a file on the neo I can't see it on the laptop.
> Moreover, when I umount it, the file are still there and, even if the
> remote directory is mounted looking at "df" the FS space used is from
> rootfs :-(
> 
> Thanks,
>   Giacomo
> 

Hi Giaomo.

 If you simples "cd /mnt/nfs", it should start working.
 Your current directory is some directory on the root filesystem.
 When you mount an NFS directory on top of that it doesn't change your
 current directory.  However if you use the full name for the directory you
 have mounted - "/mnt/nfs" - then that will lead you to the mounted
 directory, not your current directory.
 I hope that makes sense.

NeilBrown
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 828 bytes
Desc: not available
URL: <http://lists.openmoko.org/pipermail/community/attachments/20140130/26cad9f1/attachment.sig>