On Wed, May 20, 2015 at 8:24 AM, Gene Heskett <[email protected]> wrote:
> > > cd / > > mkdir /a > > mount -t nfs shop:/home /a > > ls /a > > > > What do you get? > > mount.nfs: Too many levels of symbolic links > > Here is the exports file from shop: > # /etc/exports: the access control list for filesystems which may be > exported > # to NFS clients. See exports(5). > # > # Example for NFSv2 and NFSv3: > # /srv/homes hostname1(rw,sync,no_subtree_check) hostname2 > (ro,sync,no_subtree_check) > # > # Example for NFSv4: > # /srv/nfs4 gss/krb5i(rw,sync,fsid=0,crossmnt,no_subtree_check) > # /srv/nfs4/homes gss/krb5i(rw,sync,no_subtree_check) > # > / coyote.coyote.den(rw,sync,fsid=0,no_subtree_check) > /home/ coyote.coyote.den(rw,sync,fsid=0,no_subtree_check) > > Now I note that the examples don't have a trailing / so I just took that > off and restarted everything:autofs,nfs-common,nfs-kernel-server on both > machines. > Exactly the same, except I have lost /net/lathe now. > I just found the answer in man exports, the option nohide! > So the only active line in shops exports file is now: > > / coyote.coyote.den(rw,sync,fsid=0,nohide,no_subtree_check) > I have commenetd out all the nfs mounts in fstab here on coyote, then > restarted everything, and now an ls -l of /net/shop: > root@coyote:/# ls -l /net/shop > total 104 > drwxr-xr-x 2 root root 4096 May 18 13:50 bin > drwxr-xr-x 2 root root 4096 May 18 12:11 boot > drwxr-xr-x 4 root root 4096 May 18 12:11 dev > drwxr-xr-x 131 root root 12288 May 20 07:39 etc > drwxr-xr-x 2 root root 4096 May 18 15:16 GenesAmandaHelper-0.61 > drwxr-xr-x 2 root root 4096 May 18 12:11 home > lrwxrwxrwx 1 root root 35 May 18 12:11 > initrd.img -> /boot/initrd.img-3.4-9-rtai-686-pae > drwxr-xr-x 15 root root 4096 May 18 13:23 lib > drwx------ 2 root root 16384 May 18 12:11 lost+found > drwxr-xr-x 3 root root 4096 Jul 3 2014 media > drwxr-xr-x 2 root root 4096 Apr 19 2014 mnt > drwxr-xr-x 2 root root 4096 Jul 3 2014 opt > drwxr-xr-x 2 root root 4096 Apr 19 2014 proc > drwx------ 8 root root 4096 May 18 20:24 root > drwxr-xr-x 2 root root 4096 May 18 12:28 run > drwxr-xr-x 2 root root 4096 May 18 13:51 sbin > drwxr-xr-x 2 root root 4096 Jun 10 2012 selinux > drwxr-xr-x 2 root root 4096 Jul 3 2014 srv > drwxr-xr-x 2 root root 4096 Jul 17 2013 sys > drwxrwxrwt 9 root root 4096 May 20 07:48 tmp > drwxr-xr-x 12 root root 4096 May 19 10:27 usr > drwxr-xr-x 11 root root 4096 May 18 12:18 var > lrwxrwxrwx 1 root root 31 May 18 12:18 vmlinuz -> > boot/vmlinuz-3.4-9-rtai-686-pae > > which looks good, but /net/shop/home is still empty! > > Then I noticed a flashing icon on the bottom taskbar (running not KDE > here, but TDE R14) which opened a mount configure thingy, I told it to > mount automatically, and at least till I reboot, its all working! > root@coyote:/# ls -l /net/shop/home/gene > total 44 > drwxr-xr-x 2 gene gene 4096 May 18 13:10 Desktop > drwxr-xr-x 2 gene gene 4096 May 18 13:10 Documents > drwxr-xr-x 3 gene gene 4096 May 19 16:58 Downloads > drwxr-xr-x 14 gene gene 4096 Apr 29 05:21 linuxcnc > -rw------- 1 gene gene 91 May 18 22:45 linuxcnc_debug.txt > -rw------- 1 gene gene 777 May 18 22:45 linuxcnc_print.txt > drwxr-xr-x 2 gene gene 4096 May 18 13:10 Music > drwxr-xr-x 2 gene gene 4096 May 18 13:10 Pictures > drwxr-xr-x 2 gene gene 4096 May 18 13:10 Public > drwxr-xr-x 2 gene gene 4096 May 18 13:10 Templates > drwxr-xr-x 2 gene gene 4096 May 18 13:10 Videos > > Those popups seem to correspond to my re-adding the mount lines in my > fstab here, and on reading the exports manpage, finding that I > apparently needed to set the second exports fsid=(blkid output for that > labeled partition on shop) > > So now I ought to be able to copy the amanda-client-3.3.7p1.deb from > lathe/home/gene/Downloads to shop/home/gene/Downloads, and dpkg install > the thing. After I remove the wheezy version which I have been unable > to make work, too damned many config diffs to comprehend. > > Thanks for the hand holding Mark, and I did it all before going after a > cup of the coffee I started before coming in here. > > > Mark > Okay, I missed this the first go-around. Is there some reason you are exporting the root directory? That's usually a very big no-no, since you are opening up the entire machine. Usually you just want to export the individual directories you want remote access to. Taking a SWAG, there's no separate partition for the /home dir, and you've got everything on one big partition? Exporting the / dir, then trying to export the /home dir which lives under the / dir can and will cause problems just like you have been having. Get rid of the / export. export only the directories you need access to. Or, if you really need access to the entire machine, just export the / dir, and once that's mounted on the remote machine, navigate your way to the directories you want. Mark ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
