[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
https://bugzilla.novell.com/show_bug.cgi?id=698677
https://bugzilla.novell.com/show_bug.cgi?id=698677#c1
Neil Brown
https://bugzilla.novell.com/show_bug.cgi?id=698677
https://bugzilla.novell.com/show_bug.cgi?id=698677#c2
Alex Müller
https://bugzilla.novell.com/show_bug.cgi?id=698677
https://bugzilla.novell.com/show_bug.cgi?id=698677#c3
--- Comment #3 from Neil Brown
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
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
https://bugzilla.novell.com/show_bug.cgi?id=698677
https://bugzilla.novell.com/show_bug.cgi?id=698677#c6
Hrvoje Senjan
participants (1)
-
bugzilla_noreply@novell.com