[Bug 698677] New: NFS client does not mount shares properly
https://bugzilla.novell.com/show_bug.cgi?id=698677 https://bugzilla.novell.com/show_bug.cgi?id=698677#c0 Summary: NFS client does not mount shares properly Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: 64bit OS/Version: openSUSE 11.4 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: bugzilla@go4more.de QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:2.0.1) Gecko/20100101 Firefox/4.0.1 Sorry for the vague description, I cannot find a better summary for the problem. Running "tumbleweed", since a few weeks I have a strange problem when mounting NFS shares on my Linux machine. While the shares are mounted and accessible, the system seems to consider them as unmounted. a) Mounting the shares, e.g. when changing the configuration with YaST, seemingly fails and gives an error message and /var/log/messages-entries like this: Jun 8 05:24:36 linux rpc.statd[2430]: Caught signal 15, un-registering and exiting Jun 8 05:24:36 linux sm-notify[9261]: Version 1.2.3 starting Jun 8 05:24:36 linux sm-notify[9261]: Already notifying clients; Exiting! Jun 8 05:24:36 linux rpc.statd[9279]: Version 1.2.3 starting Jun 8 05:24:36 linux rpc.statd[9279]: Flags: TI-RPC Share is mounted afterwards, though. b) Dolphin displays the NFS shares as "unmounted", consequently tries to mount them when I click on the corresponding sidebar entry. Which fails with an error, as the share is mounted nevertheless. Navigating to the share from the root drawer gives access to the share. There are similiar error reports like which relate to a change of the used portmapper for other distros. http://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg887116.html nfs-client 1.2.3-11.14.1 rpc-bind 0.2.0_git201007131952-10.2 libtirpc1 0.2.1_git201005272057-7.10.1 Reproducible: Always -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=698677 https://bugzilla.novell.com/show_bug.cgi?id=698677#c zj jia <zjjia@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zjjia@novell.com AssignedTo|bnc-team-screening@forge.pr |nfbrown@novell.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=698677 https://bugzilla.novell.com/show_bug.cgi?id=698677#c1 Neil Brown <nfbrown@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #1 from Neil Brown <nfbrown@novell.com> 2011-06-13 05:42:40 UTC --- a/ There are no error messages here. Just informational messages. rpc.statd is being stopped and restarted. No big deal. b/ Maybe a bug in dolphin... I'll see if I can reproduce the symptom tomorrow.. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=698677 https://bugzilla.novell.com/show_bug.cgi?id=698677#c2 Alex Müller <bugzilla@go4more.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bugzilla@go4more.de --- Comment #2 from Alex Müller <bugzilla@go4more.de> 2011-06-13 13:36:55 UTC --- Is it just informational that rpc quits with signal 15 when mounting devices? A similar problem: https://www.linuxquestions.org/questions/linux-networking-3/rpc-statd-not-ru... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=698677 https://bugzilla.novell.com/show_bug.cgi?id=698677#c3 --- Comment #3 from Neil Brown <nfbrown@novell.com> 2011-06-13 23:01:21 UTC ---
Is it just informational that rpc quits with signal 15 when mounting devices?
Yes. After updating the NFS shares, YaST presumably runs rcnfs restart or similar. This stops and starts all NFS servers. To stop statd it sends "SIGTERM" which is the standard way to ask a process to stop. SIGTERM == 15. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=698677 https://bugzilla.novell.com/show_bug.cgi?id=698677#c4 Neil Brown <nfbrown@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nfbrown@novell.com Component|Network |KDE4 Applications AssignedTo|nfbrown@novell.com |kde-maintainers@suse.de --- Comment #4 from Neil Brown <nfbrown@novell.com> 2011-06-14 05:07:39 UTC --- I can duplicate this problem or something a lot like it. It appears to be a problem with 'dolphin' or possibly with with the kde libraries that it uses. I'll get it assigned to someone who knows about that. I find that: 1/ When I start 'dolphin' it correctly discovers NFS mount points listed in /etc/fstab. If they are mounted and I can browse them. If they are not mounted it will try to mount them for me (which fails because I haven't given myself permission to mount them). 2/ If I use 'yast2' to add an NFS mount point while dolphin is running, dolphin sometimes notices and sometimes doesn't. When I created the mount point at a pre-existing directory it didn't notice. When I requested a new directory be created it did. However when it does notice it appears to think that the mount point is not mounted even though it is. So when I try to browse to it I get an error that the mountpoint is recorded as being mounted in mtab - which of course is correct. Dolphin should accept this as perfectly valid, rather than complain. This is the primary problem here I believe. 3/ If I manually unmount and then mount the filesystem (sudo umount /foo; sudo mount /foo), 'dolphin' will notice and the little icon in the left side bar will change. So it clearly know whether the filesystem is mounted or not. However when I try to click on that link I always get an error that dolphin tried to mount and failed. It either failed because it is already mounted (which is bad) or because I don't have permission (which is correct). So: could some KDE person please look at this - thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=698677 https://bugzilla.novell.com/show_bug.cgi?id=698677#c5 --- Comment #5 from Alex Müller <bugzilla@go4more.de> 2011-07-17 07:45:17 UTC --- I don't know whether the problem is KDE specific: Setting up the shares with YaST also gives an error message, though the shares are in reality mounted properly. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=698677 https://bugzilla.novell.com/show_bug.cgi?id=698677#c6 Hrvoje Senjan <hrvoje.senjan@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |CLOSED CC| |hrvoje.senjan@gmail.com Resolution| |FIXED --- Comment #6 from Hrvoje Senjan <hrvoje.senjan@gmail.com> 2012-11-15 22:11:10 UTC --- Closing, 11.4 reached EOL, if you can reproduce with >= 12.1 open a new BR. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com