thanks a lot!!! I tried the commands you suggested below for further debug and this one: cat /proc/net/rpc/nfsd.export/content showed me a folder that was first "mount --bind" into one of the exported folders and later it was moved from the original storage location but the "mount --bind" wasn't removed, that caused some sort of error and thus the nfs mounts were not working, once i corrected the original location of that "mount --bind" it all worked :) ----- Original Message ----- From: J. Bruce Fields <bfields@xxxxxxxxxxxx> To: Jody Gugelhupf <knueffle@xxxxxxxxx> Cc: "linux-nfs@xxxxxxxxxxxxxxx" <linux-nfs@xxxxxxxxxxxxxxx> Sent: Thursday, September 19, 2013 5:15:51 PM Subject: Re: help with nfs export/mount On Thu, Sep 19, 2013 at 07:46:32AM -0700, Jody Gugelhupf wrote: > ah ok, i have dropped the "fsid=0" as you had suggested but had still mounted with "sudo mount 192.168.2.3:/ /home/jarvis/Videos/xbmc" > though when doing tab completition on cli it does show > ls /home/jarvis/Videos/xbmc/ > ls /home/jarvis/Videos/xbmc/home > > ls /home/jarvis/Videos/xbmc/home/user > > ls /home/jarvis/Videos/xbmc/home/user/media > > ls /home/jarvis/Videos/xbmc/home/user/media/Series > > and then hangs indeed That does sound like a kernel or mountd bug. Possibly it's confused by the bind mounts. Could you post the contents of /proc/self/mounts on the server? Also, reproduce the hang as above on the client, then as root on the server, run: rpcdebug -m rpc -s cache cat /proc/net/auth.unix.ip/content cat /proc/net/rpc/nfsd.fh/content cat /proc/net/rpc/nfsd.export/content and post the output. Finally if you're up to building the latest nfs-utils and kernel from source it would be interesting to know whether the bug persists upstream. --b. > > > > > ----- Original Message ----- > From: J. Bruce Fields <bfields@xxxxxxxxxxxx> > To: Jody Gugelhupf <knueffle@xxxxxxxxx> > Cc: "linux-nfs@xxxxxxxxxxxxxxx" <linux-nfs@xxxxxxxxxxxxxxx> > Sent: Thursday, September 19, 2013 4:25:35 PM > Subject: Re: help with nfs export/mount > > On Thu, Sep 19, 2013 at 07:21:04AM -0700, Jody Gugelhupf wrote: > > on client side (in order): > > > > sudo mount 192.168.2.3:/ /home/jarvis/Videos/xbmc > > As I said, if you've dropped the "fsid=0" (which you should) then you > should be mounting the real server-side path, not /. > > > no error msg, then trying to access the directory: > > ls /home/jarvis/Videos/xbmc/home/user/media/Series > > the console does not react, > > So the mount succeeds, but the "ls" hangs? > > --b. > > > i open a new console and see again > > Sep 19 14:15:56 darkstar kernel: [61095.429346] nfs: server 192.168.2.3 OK > > Sep 19 14:17:01 darkstar kernel: [61280.169706] nfs: server 192.168.2.3 not responding, still trying > > > > > > but i also noticed this (didn't see it before) > > Sep 19 16:12:53 darkstar rpc.idmapd[576]: nss_getpwnam: name 'user' not found in domain 'localdomain' > > > > > > > > ----- Original Message ----- > > From: J. Bruce Fields <bfields@xxxxxxxxxxxx> > > To: Jody Gugelhupf <knueffle@xxxxxxxxx> > > Cc: "linux-nfs@xxxxxxxxxxxxxxx" <linux-nfs@xxxxxxxxxxxxxxx> > > Sent: Thursday, September 19, 2013 4:08:46 PM > > Subject: Re: help with nfs export/mount > > > > On Thu, Sep 19, 2013 at 07:03:30AM -0700, Jody Gugelhupf wrote: > > > on server side I see in dmesg this: > > > [8040437.603605] nfsd: last server has exited, flushing export cache > > > [8040439.496016] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory > > > [8040439.496035] NFSD: starting 90-second grace period > > > > > > on client side i only see: > > > Sep 19 13:27:56 darkstar kernel: [61095.429346] nfs: server 192.168.2.3 OK > > > Sep 19 13:31:01 darkstar kernel: [61280.169706] nfs: server 192.168.2.3 not responding, still trying > > > is there a way to further debug? > > > > Exactly what commands did you type, and what things happened, in what > > order? > > > > --b. > > > -- > To unsubscribe from this list: send the line "unsubscribe linux-nfs" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
