* help with nfs export/mount @ 2013-09-19 9:26 Jody Gugelhupf 2013-09-19 11:36 ` Malahal Naineni 2013-09-19 13:14 ` J. Bruce Fields 0 siblings, 2 replies; 15+ messages in thread From: Jody Gugelhupf @ 2013-09-19 9:26 UTC (permalink / raw) To: linux-nfs@vger.kernel.org i'm currently using samba for fileshares with my media center (xbmc/openelec on a pi). I have a server on the network with 20 different harddisks on this system that contain all my media. I have directory "/home/user/media" on my server into which i "mount --bind" all the media i want to be accessible on xbmc (on the pi) or on other computers on the local network. To give you an idea of the mounts on my server: /home/user/media#located on /dev/sda /home/user/media/Movies#located on /dev/sdf used 'mount --bind /dev/sdf/Movies /home/user/media/Movies' /home/user/media/Series#located on /dev/sda has +300 sub directories, that i created within '/home/user/media/Series' and 'mount --bind' from all other locations/hdd's into the respective folder within '/home/user/media/Series' e.g. /home/user/media/Series/24#located on /dev/sdb used 'mount --bind /dev/sdb/24 /home/user/media/Series/24' /home/user/media/Series/Star.Trek#located on /dev/sdc used 'mount --bind' and so forth but also: /home/user/media/Series/Animation#located on /dev/sda has +30 sub directories, e.g. /home/user/media/Series/Animation/Ben10#located on /dev/sdz used 'mount --bind /dev/sdz/Ben10 /home/user/media/Series/Animation/Ben10' a more elaborate list here: http://pastebin.com/DhUA5tks this all works fine, but I was told NFS would be faster so i wanted to give it a try. the server runs ubuntu 12.04.2, kernel 3.2.0-48-generic x86_64, up to date NFSv4. After installing NFS I tried simple exports (one folder without any sub directories that have no 'mount --bind' in them) and accessing them works fine. So now I thought to export the '/home/user/media' directory but using the samba setup as described from above does not work. Ideally, I would like to have to nfs mount only '/home/user/media' and have all the 'mount --bind' folders accessible on the server also accessible on all clients. Rather then using the xbmc/pi mentioned above I use my laptop with ubuntu to test the export mounts as a client. In samba it was enough to share the parent folder, in this case '/home/user/media' and everything below that share would be visible but as i understand this is not the case in nfs, I need to specify each sub directory that is 'mount --bind' (from a different file system) in the export. my export file: /home/user/media/ 192.168.2.0/24(rw,insecure,fsid=0,nohide,no_root_squash,no_subtree_check,async) /home/user/media/Movies 192.168.2.0/24(rw,insecure,nohide,no_root_squash,no_subtree_check,async) /home/user/media/Series 192.168.2.0/24(rw,insecure,nohide,no_root_squash,no_subtree_check,async) /home/user/media/Series/show_33 192.168.2.0/24(rw,insecure,nohide,no_root_squash,no_subtree_check,async) /home/user/media/Series/show_34 192.168.2.0/24(rw,insecure,nohide,no_root_squash,no_subtree_check,async) /home/user/media/Series/Animations 192.168.2.0/24(rw,insecure,nohide,no_root_squash,no_subtree_check,async) /home/user/media/Series/Animations/show_1 192.168.2.0/24(rw,insecure,nohide,no_root_squash,no_subtree_check,async) /home/user/media/Series/Animations/show_2 192.168.2.0/24(rw,insecure,nohide,no_root_squash,no_subtree_check,async) I also have tried 'crossmnt' instead of 'nohide' as I'm using a subnet and that appears to be problematic at times. /home/user/media/ 192.168.2.0/24(rw,insecure,fsid=0,crossmnt,no_root_squash,no_subtree_check,async) /home/user/media/Movies 192.168.2.0/24(rw,insecure,crossmnt,no_root_squash,no_subtree_check,async) /home/user/media/Series 192.168.2.0/24(rw,insecure,crossmnt,no_root_squash,no_subtree_check,async) /home/user/media/Series/show_33 192.168.2.0/24(rw,insecure,crossmnt,no_root_squash,no_subtree_check,async) /home/user/media/Series/show_34 192.168.2.0/24(rw,insecure,crossmnt,no_root_squash,no_subtree_check,async) /home/user/media/Series/Animations 192.168.2.0/24(rw,insecure,crossmnt,no_root_squash,no_subtree_check,async) /home/user/media/Series/Animations/show_1 192.168.2.0/24(rw,insecure,crossmnt,no_root_squash,no_subtree_check,async) /home/user/media/Series/Animations/show_2 192.168.2.0/24(rw,insecure,crossmnt,no_root_squash,no_subtree_check,async) Same result. I also have tried 'nohide' and then specified only the client IP instead of subnet info. /home/user/media/ 192.168.2.101(rw,insecure,fsid=0,nohide,no_root_squash,no_subtree_check,async) /home/user/media/Movies 192.168.2.101(rw,insecure,nohide,no_root_squash,no_subtree_check,async) /home/user/media/Series 192.168.2.101(rw,insecure,nohide,no_root_squash,no_subtree_check,async) /home/user/media/Series/show_33 192.168.2.101(rw,insecure,nohide,no_root_squash,no_subtree_check,async) /home/user/media/Series/show_34 192.168.2.101(rw,insecure,nohide,no_root_squash,no_subtree_check,async) /home/user/media/Series/Animations 192.168.2.101(rw,insecure,nohide,no_root_squash,no_subtree_check,async) /home/user/media/Series/Animations/show_1 192.168.2.101(rw,insecure,nohide,no_root_squash,no_subtree_check,async) /home/user/media/Series/Animations/show_2 192.168.2.101(rw,insecure,nohide,no_root_squash,no_subtree_check,async) Also does not work. In all the above scenarios I manage to mount on client side: sudo mount -t nfs 192.168.2.3:/home/user/media/ /home/jarvis/Videos/xbmc but when i try to mount in any of the above described scenarios i get timeout e.g.: sudo mount -t nfs 192.168.2.3:/home/user/media/Movies /home/jarvis/Videos/xbmc/Movies What I would want is to only mount the parent export on the client side, e.g.: sudo mount -t nfs 192.168.2.3:/home/user/media/ /home/jarvis/Videos/xbmc and have all directories/files that are available on the server side under '/home/user/media/' to be available on client side under '/home/jarvis/Videos/xbmc' as I have with samba at the moment how to achieve this? ^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: help with nfs export/mount 2013-09-19 9:26 help with nfs export/mount Jody Gugelhupf @ 2013-09-19 11:36 ` Malahal Naineni 2013-09-19 11:52 ` Jody Gugelhupf 2013-09-19 13:14 ` J. Bruce Fields 1 sibling, 1 reply; 15+ messages in thread From: Malahal Naineni @ 2013-09-19 11:36 UTC (permalink / raw) To: Jody Gugelhupf; +Cc: linux-nfs@vger.kernel.org Jody Gugelhupf [knueffle@yahoo.com] wrote: > i'm currently using samba for fileshares with my media center (xbmc/openelec on a pi). I have a server on the network with 20 different harddisks on this system that contain all my media. I have directory "/home/user/media" on my server into which i "mount --bind" all the media i want to be accessible on xbmc (on the pi) or on other computers on the local network. To give you an idea of the mounts on my server: > > /home/user/media#located on /dev/sda > /home/user/media/Movies#located on /dev/sdf used 'mount --bind /dev/sdf/Movies /home/user/media/Movies' > /home/user/media/Series#located on /dev/sda has +300 sub directories, that i created within '/home/user/media/Series' and 'mount --bind' from all other locations/hdd's into the respective folder within '/home/user/media/Series' e.g. > /home/user/media/Series/24#located on /dev/sdb used 'mount --bind /dev/sdb/24 /home/user/media/Series/24' > /home/user/media/Series/Star.Trek#located on /dev/sdc used 'mount --bind' and so forth but also: > /home/user/media/Series/Animation#located on /dev/sda has +30 sub directories, e.g. > /home/user/media/Series/Animation/Ben10#located on /dev/sdz used 'mount --bind /dev/sdz/Ben10 /home/user/media/Series/Animation/Ben10' > > a more elaborate list here: http://pastebin.com/DhUA5tks > > this all works fine, but I was told NFS would be faster so i wanted to give it a try. the server runs ubuntu 12.04.2, kernel 3.2.0-48-generic x86_64, up to date NFSv4. After installing NFS I tried simple exports (one folder without any sub directories that have no 'mount --bind' in them) and accessing them works fine. So now I thought to export the '/home/user/media' directory but using the samba setup as described from above does not work. Ideally, I would like to have to nfs mount only '/home/user/media' and have all the 'mount --bind' folders accessible on the server also accessible on all clients. > Rather then using the xbmc/pi mentioned above I use my laptop with ubuntu to test the export mounts as a client. In samba it was enough to share the parent folder, in this case '/home/user/media' and everything below that share would be visible but as i understand this is not the case in nfs, I need to specify each sub directory that is 'mount --bind' (from a different file system) in the export. > > my export file: > /home/user/media/ 192.168.2.0/24(rw,insecure,fsid=0,nohide,no_root_squash,no_subtree_check,async) > /home/user/media/Movies 192.168.2.0/24(rw,insecure,nohide,no_root_squash,no_subtree_check,async) > /home/user/media/Series 192.168.2.0/24(rw,insecure,nohide,no_root_squash,no_subtree_check,async) > /home/user/media/Series/show_33 192.168.2.0/24(rw,insecure,nohide,no_root_squash,no_subtree_check,async) > /home/user/media/Series/show_34 192.168.2.0/24(rw,insecure,nohide,no_root_squash,no_subtree_check,async) > /home/user/media/Series/Animations 192.168.2.0/24(rw,insecure,nohide,no_root_squash,no_subtree_check,async) > /home/user/media/Series/Animations/show_1 192.168.2.0/24(rw,insecure,nohide,no_root_squash,no_subtree_check,async) > /home/user/media/Series/Animations/show_2 192.168.2.0/24(rw,insecure,nohide,no_root_squash,no_subtree_check,async) > > I also have tried 'crossmnt' instead of 'nohide' as I'm using a subnet and that appears to be problematic at times. > /home/user/media/ 192.168.2.0/24(rw,insecure,fsid=0,crossmnt,no_root_squash,no_subtree_check,async) > /home/user/media/Movies 192.168.2.0/24(rw,insecure,crossmnt,no_root_squash,no_subtree_check,async) > /home/user/media/Series 192.168.2.0/24(rw,insecure,crossmnt,no_root_squash,no_subtree_check,async) > /home/user/media/Series/show_33 192.168.2.0/24(rw,insecure,crossmnt,no_root_squash,no_subtree_check,async) > /home/user/media/Series/show_34 192.168.2.0/24(rw,insecure,crossmnt,no_root_squash,no_subtree_check,async) > /home/user/media/Series/Animations 192.168.2.0/24(rw,insecure,crossmnt,no_root_squash,no_subtree_check,async) > /home/user/media/Series/Animations/show_1 192.168.2.0/24(rw,insecure,crossmnt,no_root_squash,no_subtree_check,async) > /home/user/media/Series/Animations/show_2 192.168.2.0/24(rw,insecure,crossmnt,no_root_squash,no_subtree_check,async) > > Same result. > > I also have tried 'nohide' and then specified only the client IP instead of subnet info. > /home/user/media/ 192.168.2.101(rw,insecure,fsid=0,nohide,no_root_squash,no_subtree_check,async) > /home/user/media/Movies 192.168.2.101(rw,insecure,nohide,no_root_squash,no_subtree_check,async) > /home/user/media/Series 192.168.2.101(rw,insecure,nohide,no_root_squash,no_subtree_check,async) > /home/user/media/Series/show_33 192.168.2.101(rw,insecure,nohide,no_root_squash,no_subtree_check,async) > /home/user/media/Series/show_34 192.168.2.101(rw,insecure,nohide,no_root_squash,no_subtree_check,async) > /home/user/media/Series/Animations 192.168.2.101(rw,insecure,nohide,no_root_squash,no_subtree_check,async) > /home/user/media/Series/Animations/show_1 192.168.2.101(rw,insecure,nohide,no_root_squash,no_subtree_check,async) > /home/user/media/Series/Animations/show_2 192.168.2.101(rw,insecure,nohide,no_root_squash,no_subtree_check,async) > > Also does not work. > > In all the above scenarios I manage to mount on client side: > sudo mount -t nfs 192.168.2.3:/home/user/media/ /home/jarvis/Videos/xbmc I am assuming this worked fine, correct? Are you using NFSv3 or V4? User (cat /proc/mounts to see if that is mounted with NFSv4 or V3). For V4, the following should work: mount 192.168.2.3:/ /home/jarvis/Videos/xbmc > but when i try to mount in any of the above described scenarios i get timeout e.g.: > > sudo mount -t nfs 192.168.2.3:/home/user/media/Movies /home/jarvis/Videos/xbmc/Movies > > What I would want is to only mount the parent export on the client side, e.g.: > sudo mount -t nfs 192.168.2.3:/home/user/media/ /home/jarvis/Videos/xbmc > and have all directories/files that are available on the server side under '/home/user/media/' to be available on client side under '/home/jarvis/Videos/xbmc' as I have with samba at the moment > > how to achieve this? You should be able to achieve this with NFSv4. Regards, Malahal. ^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: help with nfs export/mount 2013-09-19 11:36 ` Malahal Naineni @ 2013-09-19 11:52 ` Jody Gugelhupf 0 siblings, 0 replies; 15+ messages in thread From: Jody Gugelhupf @ 2013-09-19 11:52 UTC (permalink / raw) To: Malahal Naineni; +Cc: linux-nfs@vger.kernel.org thanks for the response: sudo mount -t nfs 192.168.2.3:/home/user/media/ /home/jarvis/Videos/xbmc cat /proc/mounts 192.168.2.3:/home/user/media/ /home/jarvis/Videos/xbmc nfs rw,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.2.3,mountvers=3,mountport=56597,mountproto=udp,local_lock=none,addr=192.168.2.3 0 0 so umounted and tried as you suggested: sudo mount 192.168.2.3:/ /home/jarvis/Videos/xbmc cat /proc/mounts 192.168.2.3:/ /home/jarvis/Videos/xbmc nfs4 rw,relatime,vers=4,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.2.101,minorversion=0,local_lock=none,addr=192.168.2.3 0 0 but still same problem, should i nfs mount all the subdirectories on the client side? other ideas? thank you in advance :) ----- Original Message ----- From: Malahal Naineni <malahal@us.ibm.com> To: Jody Gugelhupf <knueffle@yahoo.com> Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org> Sent: Thursday, September 19, 2013 1:36:02 PM Subject: Re: help with nfs export/mount Jody Gugelhupf [knueffle@yahoo.com] wrote: > i'm currently using samba for fileshares with my media center (xbmc/openelec on a pi). I have a server on the network with 20 different harddisks on this system that contain all my media. I have directory "/home/user/media" on my server into which i "mount --bind" all the media i want to be accessible on xbmc (on the pi) or on other computers on the local network. To give you an idea of the mounts on my server: > > /home/user/media#located on /dev/sda > /home/user/media/Movies#located on /dev/sdf used 'mount --bind /dev/sdf/Movies /home/user/media/Movies' > /home/user/media/Series#located on /dev/sda has +300 sub directories, that i created within '/home/user/media/Series' and 'mount --bind' from all other locations/hdd's into the respective folder within '/home/user/media/Series' e.g. > /home/user/media/Series/24#located on /dev/sdb used 'mount --bind /dev/sdb/24 /home/user/media/Series/24' > /home/user/media/Series/Star.Trek#located on /dev/sdc used 'mount --bind' and so forth but also: > /home/user/media/Series/Animation#located on /dev/sda has +30 sub directories, e.g. > /home/user/media/Series/Animation/Ben10#located on /dev/sdz used 'mount --bind /dev/sdz/Ben10 /home/user/media/Series/Animation/Ben10' > > a more elaborate list here: http://pastebin.com/DhUA5tks > > this all works fine, but I was told NFS would be faster so i wanted to give it a try. the server runs ubuntu 12.04.2, kernel 3.2.0-48-generic x86_64, up to date NFSv4. After installing NFS I tried simple exports (one folder without any sub directories that have no 'mount --bind' in them) and accessing them works fine. So now I thought to export the '/home/user/media' directory but using the samba setup as described from above does not work. Ideally, I would like to have to nfs mount only '/home/user/media' and have all the 'mount --bind' folders accessible on the server also accessible on all clients. > Rather then using the xbmc/pi mentioned above I use my laptop with ubuntu to test the export mounts as a client. In samba it was enough to share the parent folder, in this case '/home/user/media' and everything below that share would be visible but as i understand this is not the case in nfs, I need to specify each sub directory that is 'mount --bind' (from a different file system) in the export. > > my export file: > /home/user/media/ 192.168.2.0/24(rw,insecure,fsid=0,nohide,no_root_squash,no_subtree_check,async) > /home/user/media/Movies 192.168.2.0/24(rw,insecure,nohide,no_root_squash,no_subtree_check,async) > /home/user/media/Series 192.168.2.0/24(rw,insecure,nohide,no_root_squash,no_subtree_check,async) > /home/user/media/Series/show_33 192.168.2.0/24(rw,insecure,nohide,no_root_squash,no_subtree_check,async) > /home/user/media/Series/show_34 192.168.2.0/24(rw,insecure,nohide,no_root_squash,no_subtree_check,async) > /home/user/media/Series/Animations 192.168.2.0/24(rw,insecure,nohide,no_root_squash,no_subtree_check,async) > /home/user/media/Series/Animations/show_1 192.168.2.0/24(rw,insecure,nohide,no_root_squash,no_subtree_check,async) > /home/user/media/Series/Animations/show_2 192.168.2.0/24(rw,insecure,nohide,no_root_squash,no_subtree_check,async) > > I also have tried 'crossmnt' instead of 'nohide' as I'm using a subnet and that appears to be problematic at times. > /home/user/media/ 192.168.2.0/24(rw,insecure,fsid=0,crossmnt,no_root_squash,no_subtree_check,async) > /home/user/media/Movies 192.168.2.0/24(rw,insecure,crossmnt,no_root_squash,no_subtree_check,async) > /home/user/media/Series 192.168.2.0/24(rw,insecure,crossmnt,no_root_squash,no_subtree_check,async) > /home/user/media/Series/show_33 192.168.2.0/24(rw,insecure,crossmnt,no_root_squash,no_subtree_check,async) > /home/user/media/Series/show_34 192.168.2.0/24(rw,insecure,crossmnt,no_root_squash,no_subtree_check,async) > /home/user/media/Series/Animations 192.168.2.0/24(rw,insecure,crossmnt,no_root_squash,no_subtree_check,async) > /home/user/media/Series/Animations/show_1 192.168.2.0/24(rw,insecure,crossmnt,no_root_squash,no_subtree_check,async) > /home/user/media/Series/Animations/show_2 192.168.2.0/24(rw,insecure,crossmnt,no_root_squash,no_subtree_check,async) > > Same result. > > I also have tried 'nohide' and then specified only the client IP instead of subnet info. > /home/user/media/ 192.168.2.101(rw,insecure,fsid=0,nohide,no_root_squash,no_subtree_check,async) > /home/user/media/Movies 192.168.2.101(rw,insecure,nohide,no_root_squash,no_subtree_check,async) > /home/user/media/Series 192.168.2.101(rw,insecure,nohide,no_root_squash,no_subtree_check,async) > /home/user/media/Series/show_33 192.168.2.101(rw,insecure,nohide,no_root_squash,no_subtree_check,async) > /home/user/media/Series/show_34 192.168.2.101(rw,insecure,nohide,no_root_squash,no_subtree_check,async) > /home/user/media/Series/Animations 192.168.2.101(rw,insecure,nohide,no_root_squash,no_subtree_check,async) > /home/user/media/Series/Animations/show_1 192.168.2.101(rw,insecure,nohide,no_root_squash,no_subtree_check,async) > /home/user/media/Series/Animations/show_2 192.168.2.101(rw,insecure,nohide,no_root_squash,no_subtree_check,async) > > Also does not work. > > In all the above scenarios I manage to mount on client side: > sudo mount -t nfs 192.168.2.3:/home/user/media/ /home/jarvis/Videos/xbmc I am assuming this worked fine, correct? Are you using NFSv3 or V4? User (cat /proc/mounts to see if that is mounted with NFSv4 or V3). For V4, the following should work: mount 192.168.2.3:/ /home/jarvis/Videos/xbmc > but when i try to mount in any of the above described scenarios i get timeout e.g.: > > sudo mount -t nfs 192.168.2.3:/home/user/media/Movies /home/jarvis/Videos/xbmc/Movies > > What I would want is to only mount the parent export on the client side, e.g.: > sudo mount -t nfs 192.168.2.3:/home/user/media/ /home/jarvis/Videos/xbmc > and have all directories/files that are available on the server side under '/home/user/media/' to be available on client side under '/home/jarvis/Videos/xbmc' as I have with samba at the moment > > how to achieve this? You should be able to achieve this with NFSv4. Regards, Malahal. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: help with nfs export/mount 2013-09-19 9:26 help with nfs export/mount Jody Gugelhupf 2013-09-19 11:36 ` Malahal Naineni @ 2013-09-19 13:14 ` J. Bruce Fields 2013-09-19 13:31 ` Jody Gugelhupf 1 sibling, 1 reply; 15+ messages in thread From: J. Bruce Fields @ 2013-09-19 13:14 UTC (permalink / raw) To: Jody Gugelhupf; +Cc: linux-nfs@vger.kernel.org On Thu, Sep 19, 2013 at 02:26:46AM -0700, Jody Gugelhupf wrote: > i'm currently using samba for fileshares with my media center (xbmc/openelec on a pi). I have a server on the network with 20 different harddisks on this system that contain all my media. I have directory "/home/user/media" on my server into which i "mount --bind" all the media i want to be accessible on xbmc (on the pi) or on other computers on the local network. To give you an idea of the mounts on my server: > > /home/user/media#located on /dev/sda > /home/user/media/Movies#located on /dev/sdf used 'mount --bind /dev/sdf/Movies /home/user/media/Movies' > /home/user/media/Series#located on /dev/sda has +300 sub directories, that i created within '/home/user/media/Series' and 'mount --bind' from all other locations/hdd's into the respective folder within '/home/user/media/Series' e.g. > /home/user/media/Series/24#located on /dev/sdb used 'mount --bind /dev/sdb/24 /home/user/media/Series/24' > /home/user/media/Series/Star.Trek#located on /dev/sdc used 'mount --bind' and so forth but also: > /home/user/media/Series/Animation#located on /dev/sda has +30 sub directories, e.g. > /home/user/media/Series/Animation/Ben10#located on /dev/sdz used 'mount --bind /dev/sdz/Ben10 /home/user/media/Series/Animation/Ben10' > > a more elaborate list here: http://pastebin.com/DhUA5tks > > this all works fine, but I was told NFS would be faster so i wanted to give it a try. the server runs ubuntu 12.04.2, kernel 3.2.0-48-generic x86_64, up to date NFSv4. After installing NFS I tried simple exports (one folder without any sub directories that have no 'mount --bind' in them) and accessing them works fine. So now I thought to export the '/home/user/media' directory but using the samba setup as described from above does not work. Ideally, I would like to have to nfs mount only '/home/user/media' and have all the 'mount --bind' folders accessible on the server also accessible on all clients. > Rather then using the xbmc/pi mentioned above I use my laptop with ubuntu to test the export mounts as a client. In samba it was enough to share the parent folder, in this case '/home/user/media' and everything below that share would be visible but as i understand this is not the case in nfs, I need to specify each sub directory that is 'mount --bind' (from a different file system) in the export. No, it should actually be sufficient just to export the parent. Also, we don't recommend fsid=0 any longer. Also, "async" should be avoided. So just: /home/user/media/ 192.168.2.0/24(rw,insecure,crossmnt,no_root_check,no_subtree_check) and you mount that with "mount myserver:/home/user/media /mymountpoint". (Note the "crossmnt", which tells the server to export all the children automatically.) If that doesn't work you've probably found a bug. I'd recommend reporting that to Ubuntu, and/or here if you can reproduce with recent kernel and nfs-utils. --b. > > my export file: > /home/user/media/ 192.168.2.0/24(rw,insecure,fsid=0,nohide,no_root_squash,no_subtree_check,async) > /home/user/media/Movies 192.168.2.0/24(rw,insecure,nohide,no_root_squash,no_subtree_check,async) > /home/user/media/Series 192.168.2.0/24(rw,insecure,nohide,no_root_squash,no_subtree_check,async) > /home/user/media/Series/show_33 192.168.2.0/24(rw,insecure,nohide,no_root_squash,no_subtree_check,async) > /home/user/media/Series/show_34 192.168.2.0/24(rw,insecure,nohide,no_root_squash,no_subtree_check,async) > /home/user/media/Series/Animations 192.168.2.0/24(rw,insecure,nohide,no_root_squash,no_subtree_check,async) > /home/user/media/Series/Animations/show_1 192.168.2.0/24(rw,insecure,nohide,no_root_squash,no_subtree_check,async) > /home/user/media/Series/Animations/show_2 192.168.2.0/24(rw,insecure,nohide,no_root_squash,no_subtree_check,async) > > I also have tried 'crossmnt' instead of 'nohide' as I'm using a subnet and that appears to be problematic at times. > /home/user/media/ 192.168.2.0/24(rw,insecure,fsid=0,crossmnt,no_root_squash,no_subtree_check,async) > /home/user/media/Movies 192.168.2.0/24(rw,insecure,crossmnt,no_root_squash,no_subtree_check,async) > /home/user/media/Series 192.168.2.0/24(rw,insecure,crossmnt,no_root_squash,no_subtree_check,async) > /home/user/media/Series/show_33 192.168.2.0/24(rw,insecure,crossmnt,no_root_squash,no_subtree_check,async) > /home/user/media/Series/show_34 192.168.2.0/24(rw,insecure,crossmnt,no_root_squash,no_subtree_check,async) > /home/user/media/Series/Animations 192.168.2.0/24(rw,insecure,crossmnt,no_root_squash,no_subtree_check,async) > /home/user/media/Series/Animations/show_1 192.168.2.0/24(rw,insecure,crossmnt,no_root_squash,no_subtree_check,async) > /home/user/media/Series/Animations/show_2 192.168.2.0/24(rw,insecure,crossmnt,no_root_squash,no_subtree_check,async) > > Same result. > > I also have tried 'nohide' and then specified only the client IP instead of subnet info. > /home/user/media/ 192.168.2.101(rw,insecure,fsid=0,nohide,no_root_squash,no_subtree_check,async) > /home/user/media/Movies 192.168.2.101(rw,insecure,nohide,no_root_squash,no_subtree_check,async) > /home/user/media/Series 192.168.2.101(rw,insecure,nohide,no_root_squash,no_subtree_check,async) > /home/user/media/Series/show_33 192.168.2.101(rw,insecure,nohide,no_root_squash,no_subtree_check,async) > /home/user/media/Series/show_34 192.168.2.101(rw,insecure,nohide,no_root_squash,no_subtree_check,async) > /home/user/media/Series/Animations 192.168.2.101(rw,insecure,nohide,no_root_squash,no_subtree_check,async) > /home/user/media/Series/Animations/show_1 192.168.2.101(rw,insecure,nohide,no_root_squash,no_subtree_check,async) > /home/user/media/Series/Animations/show_2 192.168.2.101(rw,insecure,nohide,no_root_squash,no_subtree_check,async) > > Also does not work. > > In all the above scenarios I manage to mount on client side: > sudo mount -t nfs 192.168.2.3:/home/user/media/ /home/jarvis/Videos/xbmc > > but when i try to mount in any of the above described scenarios i get timeout e.g.: > > sudo mount -t nfs 192.168.2.3:/home/user/media/Movies /home/jarvis/Videos/xbmc/Movies > > What I would want is to only mount the parent export on the client side, e.g.: > sudo mount -t nfs 192.168.2.3:/home/user/media/ /home/jarvis/Videos/xbmc > and have all directories/files that are available on the server side under '/home/user/media/' to be available on client side under '/home/jarvis/Videos/xbmc' as I have with samba at the moment > > how to achieve this? > -- > To unsubscribe from this list: send the line "unsubscribe linux-nfs" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: help with nfs export/mount 2013-09-19 13:14 ` J. Bruce Fields @ 2013-09-19 13:31 ` Jody Gugelhupf 2013-09-19 13:40 ` J. Bruce Fields 0 siblings, 1 reply; 15+ messages in thread From: Jody Gugelhupf @ 2013-09-19 13:31 UTC (permalink / raw) To: J. Bruce Fields; +Cc: linux-nfs@vger.kernel.org Thanks also for your response, I have tried you suggestion of: /home/user/media/ 192.168.2.0/24(rw,insecure,crossmnt,no_root_check,no_subtree_check) but got an error that 'no_root_check' was unknown, so i suppose just a type and meant was: /home/user/media/ 192.168.2.0/24(rw,insecure,crossmnt,no_root_squash,no_subtree_check) but still it does not work, not only on ubuntu but also not on xbmc (openelec/rpi) ----- Original Message ----- From: J. Bruce Fields <bfields@fieldses.org> To: Jody Gugelhupf <knueffle@yahoo.com> Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org> Sent: Thursday, September 19, 2013 3:14:29 PM Subject: Re: help with nfs export/mount On Thu, Sep 19, 2013 at 02:26:46AM -0700, Jody Gugelhupf wrote: > i'm currently using samba for fileshares with my media center (xbmc/openelec on a pi). I have a server on the network with 20 different harddisks on this system that contain all my media. I have directory "/home/user/media" on my server into which i "mount --bind" all the media i want to be accessible on xbmc (on the pi) or on other computers on the local network. To give you an idea of the mounts on my server: > > /home/user/media#located on /dev/sda > /home/user/media/Movies#located on /dev/sdf used 'mount --bind /dev/sdf/Movies /home/user/media/Movies' > /home/user/media/Series#located on /dev/sda has +300 sub directories, that i created within '/home/user/media/Series' and 'mount --bind' from all other locations/hdd's into the respective folder within '/home/user/media/Series' e.g. > /home/user/media/Series/24#located on /dev/sdb used 'mount --bind /dev/sdb/24 /home/user/media/Series/24' > /home/user/media/Series/Star.Trek#located on /dev/sdc used 'mount --bind' and so forth but also: > /home/user/media/Series/Animation#located on /dev/sda has +30 sub directories, e.g. > /home/user/media/Series/Animation/Ben10#located on /dev/sdz used 'mount --bind /dev/sdz/Ben10 /home/user/media/Series/Animation/Ben10' > > a more elaborate list here: http://pastebin.com/DhUA5tks > > this all works fine, but I was told NFS would be faster so i wanted to give it a try. the server runs ubuntu 12.04.2, kernel 3.2.0-48-generic x86_64, up to date NFSv4. After installing NFS I tried simple exports (one folder without any sub directories that have no 'mount --bind' in them) and accessing them works fine. So now I thought to export the '/home/user/media' directory but using the samba setup as described from above does not work. Ideally, I would like to have to nfs mount only '/home/user/media' and have all the 'mount --bind' folders accessible on the server also accessible on all clients. > Rather then using the xbmc/pi mentioned above I use my laptop with ubuntu to test the export mounts as a client. In samba it was enough to share the parent folder, in this case '/home/user/media' and everything below that share would be visible but as i understand this is not the case in nfs, I need to specify each sub directory that is 'mount --bind' (from a different file system) in the export. No, it should actually be sufficient just to export the parent. Also, we don't recommend fsid=0 any longer. Also, "async" should be avoided. So just: /home/user/media/ 192.168.2.0/24(rw,insecure,crossmnt,no_root_check,no_subtree_check) and you mount that with "mount myserver:/home/user/media /mymountpoint". (Note the "crossmnt", which tells the server to export all the children automatically.) If that doesn't work you've probably found a bug. I'd recommend reporting that to Ubuntu, and/or here if you can reproduce with recent kernel and nfs-utils. --b. > > my export file: > /home/user/media/ 192.168.2.0/24(rw,insecure,fsid=0,nohide,no_root_squash,no_subtree_check,async) > /home/user/media/Movies 192.168.2.0/24(rw,insecure,nohide,no_root_squash,no_subtree_check,async) > /home/user/media/Series 192.168.2.0/24(rw,insecure,nohide,no_root_squash,no_subtree_check,async) > /home/user/media/Series/show_33 192.168.2.0/24(rw,insecure,nohide,no_root_squash,no_subtree_check,async) > /home/user/media/Series/show_34 192.168.2.0/24(rw,insecure,nohide,no_root_squash,no_subtree_check,async) > /home/user/media/Series/Animations 192.168.2.0/24(rw,insecure,nohide,no_root_squash,no_subtree_check,async) > /home/user/media/Series/Animations/show_1 192.168.2.0/24(rw,insecure,nohide,no_root_squash,no_subtree_check,async) > /home/user/media/Series/Animations/show_2 192.168.2.0/24(rw,insecure,nohide,no_root_squash,no_subtree_check,async) > > I also have tried 'crossmnt' instead of 'nohide' as I'm using a subnet and that appears to be problematic at times. > /home/user/media/ 192.168.2.0/24(rw,insecure,fsid=0,crossmnt,no_root_squash,no_subtree_check,async) > /home/user/media/Movies 192.168.2.0/24(rw,insecure,crossmnt,no_root_squash,no_subtree_check,async) > /home/user/media/Series 192.168.2.0/24(rw,insecure,crossmnt,no_root_squash,no_subtree_check,async) > /home/user/media/Series/show_33 192.168.2.0/24(rw,insecure,crossmnt,no_root_squash,no_subtree_check,async) > /home/user/media/Series/show_34 192.168.2.0/24(rw,insecure,crossmnt,no_root_squash,no_subtree_check,async) > /home/user/media/Series/Animations 192.168.2.0/24(rw,insecure,crossmnt,no_root_squash,no_subtree_check,async) > /home/user/media/Series/Animations/show_1 192.168.2.0/24(rw,insecure,crossmnt,no_root_squash,no_subtree_check,async) > /home/user/media/Series/Animations/show_2 192.168.2.0/24(rw,insecure,crossmnt,no_root_squash,no_subtree_check,async) > > Same result. > > I also have tried 'nohide' and then specified only the client IP instead of subnet info. > /home/user/media/ 192.168.2.101(rw,insecure,fsid=0,nohide,no_root_squash,no_subtree_check,async) > /home/user/media/Movies 192.168.2.101(rw,insecure,nohide,no_root_squash,no_subtree_check,async) > /home/user/media/Series 192.168.2.101(rw,insecure,nohide,no_root_squash,no_subtree_check,async) > /home/user/media/Series/show_33 192.168.2.101(rw,insecure,nohide,no_root_squash,no_subtree_check,async) > /home/user/media/Series/show_34 192.168.2.101(rw,insecure,nohide,no_root_squash,no_subtree_check,async) > /home/user/media/Series/Animations 192.168.2.101(rw,insecure,nohide,no_root_squash,no_subtree_check,async) > /home/user/media/Series/Animations/show_1 192.168.2.101(rw,insecure,nohide,no_root_squash,no_subtree_check,async) > /home/user/media/Series/Animations/show_2 192.168.2.101(rw,insecure,nohide,no_root_squash,no_subtree_check,async) > > Also does not work. > > In all the above scenarios I manage to mount on client side: > sudo mount -t nfs 192.168.2.3:/home/user/media/ /home/jarvis/Videos/xbmc > > but when i try to mount in any of the above described scenarios i get timeout e.g.: > > sudo mount -t nfs 192.168.2.3:/home/user/media/Movies /home/jarvis/Videos/xbmc/Movies > > What I would want is to only mount the parent export on the client side, e.g.: > sudo mount -t nfs 192.168.2.3:/home/user/media/ /home/jarvis/Videos/xbmc > and have all directories/files that are available on the server side under '/home/user/media/' to be available on client side under '/home/jarvis/Videos/xbmc' as I have with samba at the moment > > how to achieve this? > -- > To unsubscribe from this list: send the line "unsubscribe linux-nfs" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: help with nfs export/mount 2013-09-19 13:31 ` Jody Gugelhupf @ 2013-09-19 13:40 ` J. Bruce Fields 2013-09-19 14:03 ` Jody Gugelhupf 0 siblings, 1 reply; 15+ messages in thread From: J. Bruce Fields @ 2013-09-19 13:40 UTC (permalink / raw) To: Jody Gugelhupf; +Cc: linux-nfs@vger.kernel.org On Thu, Sep 19, 2013 at 06:31:41AM -0700, Jody Gugelhupf wrote: > Thanks also for your response, I have tried you suggestion of: > /home/user/media/ 192.168.2.0/24(rw,insecure,crossmnt,no_root_check,no_subtree_check) > > but got an error that 'no_root_check' was unknown, so i suppose just a type and meant was: > /home/user/media/ 192.168.2.0/24(rw,insecure,crossmnt,no_root_squash,no_subtree_check) > > > but still it does not work, not only on ubuntu but also not on xbmc (openelec/rpi) Could you explain exactly how it fails? --b. ^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: help with nfs export/mount 2013-09-19 13:40 ` J. Bruce Fields @ 2013-09-19 14:03 ` Jody Gugelhupf 2013-09-19 14:08 ` J. Bruce Fields 0 siblings, 1 reply; 15+ messages in thread From: Jody Gugelhupf @ 2013-09-19 14:03 UTC (permalink / raw) To: J. Bruce Fields; +Cc: linux-nfs@vger.kernel.org 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? ----- Original Message ----- From: J. Bruce Fields <bfields@fieldses.org> To: Jody Gugelhupf <knueffle@yahoo.com> Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org> Sent: Thursday, September 19, 2013 3:40:28 PM Subject: Re: help with nfs export/mount On Thu, Sep 19, 2013 at 06:31:41AM -0700, Jody Gugelhupf wrote: > Thanks also for your response, I have tried you suggestion of: > /home/user/media/ 192.168.2.0/24(rw,insecure,crossmnt,no_root_check,no_subtree_check) > > but got an error that 'no_root_check' was unknown, so i suppose just a type and meant was: > /home/user/media/ 192.168.2.0/24(rw,insecure,crossmnt,no_root_squash,no_subtree_check) > > > but still it does not work, not only on ubuntu but also not on xbmc (openelec/rpi) Could you explain exactly how it fails? --b. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: help with nfs export/mount 2013-09-19 14:03 ` Jody Gugelhupf @ 2013-09-19 14:08 ` J. Bruce Fields 2013-09-19 14:21 ` Jody Gugelhupf 0 siblings, 1 reply; 15+ messages in thread From: J. Bruce Fields @ 2013-09-19 14:08 UTC (permalink / raw) To: Jody Gugelhupf; +Cc: linux-nfs@vger.kernel.org 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. ^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: help with nfs export/mount 2013-09-19 14:08 ` J. Bruce Fields @ 2013-09-19 14:21 ` Jody Gugelhupf 2013-09-19 14:25 ` J. Bruce Fields 0 siblings, 1 reply; 15+ messages in thread From: Jody Gugelhupf @ 2013-09-19 14:21 UTC (permalink / raw) To: J. Bruce Fields; +Cc: linux-nfs@vger.kernel.org on client side (in order): sudo mount 192.168.2.3:/ /home/jarvis/Videos/xbmc no error msg, then trying to access the directory: ls /home/jarvis/Videos/xbmc/home/user/media/Series the console does not react, 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@fieldses.org> To: Jody Gugelhupf <knueffle@yahoo.com> Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org> 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. ^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: help with nfs export/mount 2013-09-19 14:21 ` Jody Gugelhupf @ 2013-09-19 14:25 ` J. Bruce Fields 2013-09-19 14:46 ` Jody Gugelhupf 0 siblings, 1 reply; 15+ messages in thread From: J. Bruce Fields @ 2013-09-19 14:25 UTC (permalink / raw) To: Jody Gugelhupf; +Cc: linux-nfs@vger.kernel.org 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@fieldses.org> > To: Jody Gugelhupf <knueffle@yahoo.com> > Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org> > 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. > ^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: help with nfs export/mount 2013-09-19 14:25 ` J. Bruce Fields @ 2013-09-19 14:46 ` Jody Gugelhupf 2013-09-19 15:15 ` J. Bruce Fields 0 siblings, 1 reply; 15+ messages in thread From: Jody Gugelhupf @ 2013-09-19 14:46 UTC (permalink / raw) To: J. Bruce Fields; +Cc: linux-nfs@vger.kernel.org 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 ----- Original Message ----- From: J. Bruce Fields <bfields@fieldses.org> To: Jody Gugelhupf <knueffle@yahoo.com> Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org> 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@fieldses.org> > To: Jody Gugelhupf <knueffle@yahoo.com> > Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org> > 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: help with nfs export/mount 2013-09-19 14:46 ` Jody Gugelhupf @ 2013-09-19 15:15 ` J. Bruce Fields 2013-09-21 10:51 ` Jody Gugelhupf 0 siblings, 1 reply; 15+ messages in thread From: J. Bruce Fields @ 2013-09-19 15:15 UTC (permalink / raw) To: Jody Gugelhupf; +Cc: linux-nfs@vger.kernel.org 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@fieldses.org> > To: Jody Gugelhupf <knueffle@yahoo.com> > Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org> > 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@fieldses.org> > > To: Jody Gugelhupf <knueffle@yahoo.com> > > Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org> > > 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@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > ^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: help with nfs export/mount 2013-09-19 15:15 ` J. Bruce Fields @ 2013-09-21 10:51 ` Jody Gugelhupf 2013-09-21 14:36 ` Jody Gugelhupf 0 siblings, 1 reply; 15+ messages in thread From: Jody Gugelhupf @ 2013-09-21 10:51 UTC (permalink / raw) To: J. Bruce Fields; +Cc: linux-nfs@vger.kernel.org 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@fieldses.org> To: Jody Gugelhupf <knueffle@yahoo.com> Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org> 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@fieldses.org> > To: Jody Gugelhupf <knueffle@yahoo.com> > Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org> > 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@fieldses.org> > > To: Jody Gugelhupf <knueffle@yahoo.com> > > Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org> > > 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@vger.kernel.org > 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: help with nfs export/mount 2013-09-21 10:51 ` Jody Gugelhupf @ 2013-09-21 14:36 ` Jody Gugelhupf 2013-09-21 14:46 ` J. Bruce Fields 0 siblings, 1 reply; 15+ messages in thread From: Jody Gugelhupf @ 2013-09-21 14:36 UTC (permalink / raw) To: Jody Gugelhupf, J. Bruce Fields; +Cc: linux-nfs@vger.kernel.org but now my syslog and dmesg on nfs serverside is full of these msg'es: Sep 21 16:34:13 fatzo kernel: [8295937.032636] RPC: Want update, refage=120, age=116 Sep 21 16:34:21 fatzo kernel: [8295945.056091] RPC: Want update, refage=120, age=0 Sep 21 16:34:26 fatzo kernel: [8295950.056027] RPC: Want update, refage=120, age=5 Sep 21 16:34:31 fatzo kernel: [8295955.056024] RPC: Want update, refage=120, age=10 Sep 21 16:34:36 fatzo kernel: [8295960.056024] RPC: Want update, refage=120, age=15 Sep 21 16:34:41 fatzo kernel: [8295965.056095] RPC: Want update, refage=120, age=20 Sep 21 16:34:46 fatzo kernel: [8295970.056030] RPC: Want update, refage=120, age=25 Sep 21 16:34:51 fatzo kernel: [8295975.056046] RPC: Want update, refage=120, age=30 Sep 21 16:35:05 fatzo kernel: [8295989.155466] RPC: Want update, refage=120, age=44 Sep 21 16:35:10 fatzo kernel: [8295994.152029] RPC: Want update, refage=120, age=49 Sep 21 16:35:15 fatzo kernel: [8295999.152050] RPC: Want update, refage=120, age=54 Sep 21 16:35:26 fatzo kernel: [8296010.195221] RPC: Want update, refage=120, age=65 Sep 21 16:35:31 fatzo kernel: [8296015.192028] RPC: Want update, refage=120, age=70 Sep 21 16:35:47 fatzo kernel: [8296031.235390] RPC: Want update, refage=120, age=86 Sep 21 16:35:52 fatzo kernel: [8296036.232029] RPC: Want update, refage=120, age=91 Sep 21 16:35:57 fatzo kernel: [8296041.232100] RPC: Want update, refage=120, age=96 Sep 21 16:36:08 fatzo kernel: [8296052.275643] RPC: Want update, refage=120, age=107 Sep 21 16:36:13 fatzo kernel: [8296057.272027] RPC: Want update, refage=120, age=112 Sep 21 16:36:29 fatzo kernel: [8296073.315985] RPC: Want update, refage=120, age=0 Sep 21 16:36:34 fatzo kernel: [8296078.312026] RPC: Want update, refage=120, age=5 Sep 21 16:36:39 fatzo kernel: [8296083.312096] RPC: Want update, refage=120, age=10 Sep 21 16:36:50 fatzo kernel: [8296094.356721] RPC: Want update, refage=120, age=21 Sep 21 16:36:55 fatzo kernel: [8296099.356097] RPC: Want update, refage=120, age=26 Sep 21 16:37:03 fatzo kernel: [8296107.389078] RPC: Want update, refage=1800, age=903 Sep 21 16:37:11 fatzo kernel: [8296115.367365] RPC: Want update, refage=120, age=42 Sep 21 16:37:16 fatzo kernel: [8296120.364090] RPC: Want update, refage=120, age=47 Sep 21 16:37:21 fatzo kernel: [8296125.364043] RPC: Want update, refage=120, age=52 Sep 21 16:37:33 fatzo kernel: [8296136.418063] RPC: Want update, refage=120, age=63 Sep 21 16:37:38 fatzo kernel: [8296141.416131] RPC: Want update, refage=120, age=68 Sep 21 16:37:54 fatzo kernel: [8296157.441174] RPC: Want update, refage=120, age=85 Sep 21 16:37:59 fatzo kernel: [8296162.440067] RPC: Want update, refage=120, age=90 Sep 21 16:38:04 fatzo kernel: [8296167.440097] RPC: Want update, refage=120, age=95 Sep 21 16:38:15 fatzo kernel: [8296178.501474] RPC: Want update, refage=120, age=106 Sep 21 16:38:19 fatzo kernel: [8296182.467950] RPC: Want update, refage=1800, age=907 Sep 21 16:38:20 fatzo kernel: [8296183.500042] RPC: Want update, refage=120, age=111 Sep 21 16:38:35 fatzo kernel: [8296198.952120] RPC: Want update, refage=120, age=0 Sep 21 16:38:40 fatzo kernel: [8296203.952047] RPC: Want update, refage=120, age=5 Sep 21 16:38:45 fatzo kernel: [8296208.952030] RPC: Want update, refage=120, age=10 Sep 21 16:38:50 fatzo kernel: [8296213.952032] RPC: Want update, refage=120, age=15 Sep 21 16:38:55 fatzo kernel: [8296218.952025] RPC: Want update, refage=120, age=20 Sep 21 16:39:00 fatzo kernel: [8296223.953579] RPC: Want update, refage=120, age=20 tired to find something about this but not much returned, ----- Original Message ----- From: Jody Gugelhupf <knueffle@yahoo.com> To: J. Bruce Fields <bfields@fieldses.org> Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org> Sent: Saturday, September 21, 2013 12:51:26 PM Subject: Re: help with nfs export/mount 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@fieldses.org> To: Jody Gugelhupf <knueffle@yahoo.com> Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org> 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@fieldses.org> > To: Jody Gugelhupf <knueffle@yahoo.com> > Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org> > 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@fieldses.org> > > To: Jody Gugelhupf <knueffle@yahoo.com> > > Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org> > > 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@vger.kernel.org > 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@vger.kernel.org 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: help with nfs export/mount 2013-09-21 14:36 ` Jody Gugelhupf @ 2013-09-21 14:46 ` J. Bruce Fields 0 siblings, 0 replies; 15+ messages in thread From: J. Bruce Fields @ 2013-09-21 14:46 UTC (permalink / raw) To: Jody Gugelhupf; +Cc: linux-nfs@vger.kernel.org On Sat, Sep 21, 2013 at 07:36:24AM -0700, Jody Gugelhupf wrote: > but now my syslog and dmesg on nfs serverside is full of these msg'es: rpcdebug -m rpc -c all --b. > > Sep 21 16:34:13 fatzo kernel: [8295937.032636] RPC: Want update, refage=120, age=116 > Sep 21 16:34:21 fatzo kernel: [8295945.056091] RPC: Want update, refage=120, age=0 > Sep 21 16:34:26 fatzo kernel: [8295950.056027] RPC: Want update, refage=120, age=5 > Sep 21 16:34:31 fatzo kernel: [8295955.056024] RPC: Want update, refage=120, age=10 > Sep 21 16:34:36 fatzo kernel: [8295960.056024] RPC: Want update, refage=120, age=15 > Sep 21 16:34:41 fatzo kernel: [8295965.056095] RPC: Want update, refage=120, age=20 > Sep 21 16:34:46 fatzo kernel: [8295970.056030] RPC: Want update, refage=120, age=25 > Sep 21 16:34:51 fatzo kernel: [8295975.056046] RPC: Want update, refage=120, age=30 > Sep 21 16:35:05 fatzo kernel: [8295989.155466] RPC: Want update, refage=120, age=44 > Sep 21 16:35:10 fatzo kernel: [8295994.152029] RPC: Want update, refage=120, age=49 > Sep 21 16:35:15 fatzo kernel: [8295999.152050] RPC: Want update, refage=120, age=54 > Sep 21 16:35:26 fatzo kernel: [8296010.195221] RPC: Want update, refage=120, age=65 > Sep 21 16:35:31 fatzo kernel: [8296015.192028] RPC: Want update, refage=120, age=70 > Sep 21 16:35:47 fatzo kernel: [8296031.235390] RPC: Want update, refage=120, age=86 > Sep 21 16:35:52 fatzo kernel: [8296036.232029] RPC: Want update, refage=120, age=91 > Sep 21 16:35:57 fatzo kernel: [8296041.232100] RPC: Want update, refage=120, age=96 > Sep 21 16:36:08 fatzo kernel: [8296052.275643] RPC: Want update, refage=120, age=107 > Sep 21 16:36:13 fatzo kernel: [8296057.272027] RPC: Want update, refage=120, age=112 > Sep 21 16:36:29 fatzo kernel: [8296073.315985] RPC: Want update, refage=120, age=0 > Sep 21 16:36:34 fatzo kernel: [8296078.312026] RPC: Want update, refage=120, age=5 > Sep 21 16:36:39 fatzo kernel: [8296083.312096] RPC: Want update, refage=120, age=10 > Sep 21 16:36:50 fatzo kernel: [8296094.356721] RPC: Want update, refage=120, age=21 > Sep 21 16:36:55 fatzo kernel: [8296099.356097] RPC: Want update, refage=120, age=26 > Sep 21 16:37:03 fatzo kernel: [8296107.389078] RPC: Want update, refage=1800, age=903 > Sep 21 16:37:11 fatzo kernel: [8296115.367365] RPC: Want update, refage=120, age=42 > Sep 21 16:37:16 fatzo kernel: [8296120.364090] RPC: Want update, refage=120, age=47 > Sep 21 16:37:21 fatzo kernel: [8296125.364043] RPC: Want update, refage=120, age=52 > Sep 21 16:37:33 fatzo kernel: [8296136.418063] RPC: Want update, refage=120, age=63 > Sep 21 16:37:38 fatzo kernel: [8296141.416131] RPC: Want update, refage=120, age=68 > Sep 21 16:37:54 fatzo kernel: [8296157.441174] RPC: Want update, refage=120, age=85 > Sep 21 16:37:59 fatzo kernel: [8296162.440067] RPC: Want update, refage=120, age=90 > Sep 21 16:38:04 fatzo kernel: [8296167.440097] RPC: Want update, refage=120, age=95 > Sep 21 16:38:15 fatzo kernel: [8296178.501474] RPC: Want update, refage=120, age=106 > Sep 21 16:38:19 fatzo kernel: [8296182.467950] RPC: Want update, refage=1800, age=907 > Sep 21 16:38:20 fatzo kernel: [8296183.500042] RPC: Want update, refage=120, age=111 > Sep 21 16:38:35 fatzo kernel: [8296198.952120] RPC: Want update, refage=120, age=0 > Sep 21 16:38:40 fatzo kernel: [8296203.952047] RPC: Want update, refage=120, age=5 > Sep 21 16:38:45 fatzo kernel: [8296208.952030] RPC: Want update, refage=120, age=10 > Sep 21 16:38:50 fatzo kernel: [8296213.952032] RPC: Want update, refage=120, age=15 > Sep 21 16:38:55 fatzo kernel: [8296218.952025] RPC: Want update, refage=120, age=20 > Sep 21 16:39:00 fatzo kernel: [8296223.953579] RPC: Want update, refage=120, age=20 > tired to find something about this but not much returned, > > > > ----- Original Message ----- > From: Jody Gugelhupf <knueffle@yahoo.com> > To: J. Bruce Fields <bfields@fieldses.org> > Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org> > Sent: Saturday, September 21, 2013 12:51:26 PM > Subject: Re: help with nfs export/mount > > 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@fieldses.org> > To: Jody Gugelhupf <knueffle@yahoo.com> > Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org> > 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@fieldses.org> > > To: Jody Gugelhupf <knueffle@yahoo.com> > > Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org> > > 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@fieldses.org> > > > To: Jody Gugelhupf <knueffle@yahoo.com> > > > Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org> > > > 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@vger.kernel.org > > 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@vger.kernel.org > 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@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > ^ permalink raw reply [flat|nested] 15+ messages in thread
end of thread, other threads:[~2013-09-21 14:46 UTC | newest] Thread overview: 15+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2013-09-19 9:26 help with nfs export/mount Jody Gugelhupf 2013-09-19 11:36 ` Malahal Naineni 2013-09-19 11:52 ` Jody Gugelhupf 2013-09-19 13:14 ` J. Bruce Fields 2013-09-19 13:31 ` Jody Gugelhupf 2013-09-19 13:40 ` J. Bruce Fields 2013-09-19 14:03 ` Jody Gugelhupf 2013-09-19 14:08 ` J. Bruce Fields 2013-09-19 14:21 ` Jody Gugelhupf 2013-09-19 14:25 ` J. Bruce Fields 2013-09-19 14:46 ` Jody Gugelhupf 2013-09-19 15:15 ` J. Bruce Fields 2013-09-21 10:51 ` Jody Gugelhupf 2013-09-21 14:36 ` Jody Gugelhupf 2013-09-21 14:46 ` J. Bruce Fields
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).