Mailinglist Archive: opensuse-bugs (4297 mails)

< Previous Next >
[Bug 765291] New: nfs client can't mount anything: Starting rpc.statd ... portmapper not running
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Mon, 4 Jun 2012 11:51:44 +0000
  • Message-id: <>

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@xxxxxxxxxxxxxxxxxxxxxx
ReportedBy: drmeier@xxxxxx
QAContact: qa-bugs@xxxxxxx
Found By: ---
Blocker: ---

User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20100101

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.

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
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:
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >