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
