It seems that NFS is really pooched in 12.1. I have never had so many issues with it.
For some reason, NFS in 12.1 keeps trying to mount the NFS shares twice. This causes all kinds of messages during boot and shut down with it trying to mount and unmount the extra shares. Even in Yast Partitioner it shows up twice.
I am not running NFSv4 because it does not support _netdev which adds a whole other can of worms to bootups with it trying to mount before the service starts.
Using systemd or sysvinit does not change anything.
There is only one line in fstab regarding the mount:
Just a hunch: maybe the new systemd is troubling the networking. Try deleting the RPM “systemd-sysvinit” and instead install “sysvinit-init”. I needed to do that for cifs mounts to work, hence the hunch re NFS mounts. If not useful, you can reverse it.
On 01/24/2012 06:36 AM, deanjo13 wrote:
>
> swerdna;2433562 Wrote:
>> Just a hunch: maybe the new systemd is troubling the networking. Try
>> deleting the RPM “systemd-sysvinit” and instead install “sysvinit-init”.
>> I needed to do that for cifs mounts to work, hence the hunch re NFS
>> mounts. If not useful, you can reverse it.
>
> That was the first thing I tried, thanks for the suggestion however.
Mounting on demand has it’s own set of issues. This really shouldn’t be all that hard to do, NFS has worked fine with the same setup here since before openSUSE days when it was still SuSE.
On 2012-01-24 13:16, deanjo13 wrote:
>
> It seems that NFS is really pooched in 12.1. I have never had so many
> issues with it.
>
> For some reason, NFS in 12.1 keeps trying to mount the NFS shares
> twice. This causes all kinds of messages during boot and shut down with
> it trying to mount and unmount the extra shares. Even in Yast
> Partitioner it shows up twice.
I use NFS client on 12.1 with the server on 11.4, I see no problems. :-?
> Elanor:~ # mount | grep -i nfs
> rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime)
> Telcontar.valinor:/data/storage_c/repositorios_zypp/ on /var/cache/zypp/nfs_packages type nfs4 (rw,relatime,vers=4,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.74.131,minorversion=0,local_lock=none,addr=192.168.1.14,_netdev)
> Elanor:~ #
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
Anybody else have any ideas? It is getting to be a real pain as when you have a lot of nfs mounts it takes forever for konqueror to appear do to it trying to read those duplicate mounts.
On 01/29/2012 02:26 PM, deanjo13 wrote:
>
> Anybody else have any ideas? It is getting to be a real pain as when
> you have a lot of nfs mounts it takes forever for konqueror to appear do
> to it trying to read those duplicate mounts.
You rejected the only solution I had. You are on your own.
I am reading this with interest because I still need to go beyond 11.2 and 11.4 on my systems and a not functioning NFS would be a severe showstopper.
I agree thatt NFS simply should function. Would be idiot when it was dropped after so many years in Unix/Linux.
But atm I can not help you with any tests because I have only a 12.1 test system bootable on the server and not on the client.
Thus a wild suggestion. Does it help when that _netdev option is left out? Not as a solution (I guess you need it for some reason), but just to test if that double mount is gone.
And of course it would have been better and easier to prove your double mount by posting the output of
_netdev is required or it tries to mount the share before the service starts (happens with systemd or sysvinit)
The output of mount
dean@nemicron:~> mount
devtmpfs on /dev type devtmpfs (rw,relatime,size=4055944k,nr_inodes=1013986,mode=755)
tmpfs on /dev/shm type tmpfs (rw,relatime)
tmpfs on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620,ptmxmode=000)
/dev/sdd1 on / type ext4 (rw,relatime,user_xattr,acl,barrier=1,data=ordered)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
securityfs on /sys/kernel/security type securityfs (rw,relatime)
/dev/sda1 on /home type xfs (rw,relatime,attr2,delaylog,noquota)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
/dev/sde3 on /local/WinData type fuseblk (rw,nosuid,nodev,noexec,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096)
/dev/sdg1 on /local/WinMedia type fuseblk (rw,nosuid,nodev,noexec,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096)
/dev/sde2 on /local/WinSys type fuseblk (rw,nosuid,nodev,noexec,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096)
/dev/sdf1 on /local/Hitachi type xfs (rw,relatime,attr2,delaylog,noquota)
/dev/sdc1 on /local/WD1000 type xfs (rw,relatime,attr2,delaylog,noquota)
/dev/sdd3 on /local/WD900 type xfs (rw,relatime,attr2,delaylog,noquota)
/dev/sdb1 on /local/Hitach_2 type xfs (rw,relatime,attr2,delaylog,noquota)
tmpfs on /var/lock type tmpfs (rw,nosuid,nodev,relatime,mode=755)
tmpfs on /var/run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
tmpfs on /media type tmpfs (rw,nosuid,nodev,relatime,mode=755)
nfsd on /proc/fs/nfsd type nfsd (rw,relatime)
192.168.1.201:/local/2000-1/ on /local/2000-1 type nfs (rw,relatime,vers=3,rsize=262144,wsize=262144,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.1.201,mountvers=3,mountport=43158,mountproto=udp,local_lock=none,addr=192.168.1.201,_netdev)
192.168.1.201:/local/2000-2/ on /local/2000-2 type nfs (rw,relatime,vers=3,rsize=262144,wsize=262144,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.1.201,mountvers=3,mountport=43158,mountproto=udp,local_lock=none,addr=192.168.1.201,_netdev)
192.168.1.201:/local/2000-3/ on /local/2000-3 type nfs (rw,relatime,vers=3,rsize=262144,wsize=262144,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.1.201,mountvers=3,mountport=43158,mountproto=udp,local_lock=none,addr=192.168.1.201,_netdev)
192.168.1.201:/local/2000-4/ on /local/2000-4 type nfs (rw,relatime,vers=3,rsize=262144,wsize=262144,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.1.201,mountvers=3,mountport=43158,mountproto=udp,local_lock=none,addr=192.168.1.201,_netdev)
192.168.1.201:/local/2000-5/ on /local/2000-5 type nfs (rw,relatime,vers=3,rsize=262144,wsize=262144,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.1.201,mountvers=3,mountport=43158,mountproto=udp,local_lock=none,addr=192.168.1.201,_netdev)
192.168.1.201:/local/S500/ on /local/S500 type nfs (rw,relatime,vers=3,rsize=262144,wsize=262144,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.1.201,mountvers=3,mountport=43158,mountproto=udp,local_lock=none,addr=192.168.1.201,_netdev)
gvfs-fuse-daemon on /home/dean/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,relatime,user_id=1000,group_id=100)
It’s really frustrating as the shares were working perfectly fine in earlier versions of openSUSE. Also when using the partitioner on anything when it goes to apply the changes it pops up error after error after applying the changes because it cannot access those phantom mounts. I only have a few mounts in this setup and would like to get it resolved before adding the other NFS shares.
Sorry, I was away last week and I see now that nobody came to help you any further. I tried to reread and understand what your problem is and what evidence we have. Apart from the two windows from some GUI (which is not realy something I would use as evidence for something except for finding bugs in that GUI application), we have an fstab wich says (among other things):
Then I asked you for the output of mount to prove the double mounting and you posted:
192.168.1.201:/local/2000-1/ on /local/2000-1 type nfs (rw,relatime,vers=3,rsize=262144,wsize=262144,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.1.201,mountvers=3,mountport=43158,mountproto=udp,local_lock=none,addr=192.168.1.201,_netdev)
192.168.1.201:/local/2000-2/ on /local/2000-2 type nfs (rw,relatime,vers=3,rsize=262144,wsize=262144,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.1.201,mountvers=3,mountport=43158,mountproto=udp,local_lock=none,addr=192.168.1.201,_netdev)
192.168.1.201:/local/2000-3/ on /local/2000-3 type nfs (rw,relatime,vers=3,rsize=262144,wsize=262144,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.1.201,mountvers=3,mountport=43158,mountproto=udp,local_lock=none,addr=192.168.1.201,_netdev)
192.168.1.201:/local/2000-4/ on /local/2000-4 type nfs (rw,relatime,vers=3,rsize=262144,wsize=262144,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.1.201,mountvers=3,mountport=43158,mountproto=udp,local_lock=none,addr=192.168.1.201,_netdev)
192.168.1.201:/local/2000-5/ on /local/2000-5 type nfs (rw,relatime,vers=3,rsize=262144,wsize=262144,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.1.201,mountvers=3,mountport=43158,mountproto=udp,local_lock=none,addr=192.168.1.201,_netdev)
192.168.1.201:/local/S500/ on /local/S500 type nfs (rw,relatime,vers=3,rsize=262144,wsize=262144,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.1.201,mountvers=3,mountport=43158,mountproto=udp,local_lock=none,addr=192.168.1.201,_netdev)
which I can not interprete as a double mount of what fstab asks for.
Are these two things realy consistent with each other?
And you also talk about “This causes all kinds of messages during boot and shut down with it trying to mount and unmount the extra shares” (I guess you mean “NFS remote mounts” with “shares”), but you do not show us anything of it.
One thiing I can say about the nfs entry in fstab: I don’t have the “_netdev” in the clients’ fstab (which all work fine).
A bit of advice: start using Yast2-Network services-NFS server and NFS client to configure the NFS shares and mounts, leave all default.
Found out that the “_netdev” thingy forces nfs to wait for the network adapters to be ready. Could the OP be better off using Sysinit V, instead of systemd?
I am not running NFSv4 because it does not support _netdev which adds a whole other can of worms to bootups with it trying to mount before the service starts.
Using systemd or sysvinit does not change anything.
Which I admit I do not quite understand because I never had such problems about trying to start a service (which one?).
That message will repeat on every NFS mount because of the duplicate. Without the _netdev option it quite literally takes over 20 minutes to boot a system in 11.4 or 12.1 client with 5 NFS mounts because it tries to mount them before the network is even up (and this isn’t even a DHCP issue as the machines are setup for static IPv4 addresses) and as a result has to timeout on each attempt before continuing on. Again this behavior is seen with systemd or sysvinit.
Maybe due to the discussion between Knurpht and me, you forgot to look at my first question in post #13 above: is this fstab listing consistent with the mount listing, that means do they belong to the same system in the same situation (that is short after boot, in any case before all sorts of (un)mounts are done by the system manager?
I ask because I see only one (1) NFS mount in fstab ((let we call it for short* 2000-4*) and I see six (6) NFS mounts in the mount list where only one (1) is about 2000-4 and thus I do not see 2000-4 mounted twice.
That’s because the second attempt to mount fails and thus would not show up in the list as it only shows what has successfully mounted (the contents of mtab).
The programs mount and umount maintain a list of currently mounted filesystems in the file /etc/mtab. If no arguments are given to mount, this list is printed.
