[Bug 765291] New: nfs client can't mount anything: Starting rpc.statd ... portmapper not running
https://bugzilla.novell.com/show_bug.cgi?id=765291 https://bugzilla.novell.com/show_bug.cgi?id=765291#c0 Summary: nfs client can't mount anything: Starting rpc.statd ... portmapper not running Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: openSUSE 12.1 Status: NEW Severity: Major Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: drmeier@gmx.de QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20100101 Firefox/12.0 System: openSUSE 12.1 updated from openSUSE 11.4 Init: systemd, but same happens with sysvinit I think this problem was already discussed in the bug mentioned below, but i don't see the solution has been posted in the bug. https://bugzilla.novell.com/show_bug.cgi?id=732563 Reproducible: Always Steps to Reproduce: 1. enter a new nfs share in the NFS-Client task in Yast2 2. the share can be choosen from the menue 3. after clicking OK, Yast2 says that mounting has failed 4. trying to mount the share on the commandline gives the following error: Starting rpc.statd ... portmapper not running failed mount.nfs: rpc.statd is not running but is required for remote locking. mount.nfs: Either use '-o nolock' to keep locks local, or start statd. mount.nfs: an incorrect mount option was specified Actual Results: NFS folder has not been mounted. Expected Results: NFS folder should have been mounted. The fstab looks like this: meiernas:/volume1/homes /mnt/meiernas_homes nfs defaults 0 0 /var/log/messages says nothing, dmesg says nothing. -- 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=765291 https://bugzilla.novell.com/show_bug.cgi?id=765291#c kk zhang <kkzhang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kkzhang@suse.com AssignedTo|bnc-team-screening@forge.pr |dmueller@suse.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=765291 https://bugzilla.novell.com/show_bug.cgi?id=765291#c D Meier <drmeier@gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High -- 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=765291 https://bugzilla.novell.com/show_bug.cgi?id=765291#c Dirk Mueller <dmueller@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|dmueller@suse.com |mvidner@suse.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=765291 https://bugzilla.novell.com/show_bug.cgi?id=765291#c1 D Meier <drmeier@gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID --- Comment #1 from D Meier <drmeier@gmx.de> 2012-10-14 16:39:01 UTC --- Seems that mount with option "-o nolocks" really solves that problem. -- 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