Mailinglist Archive: opensuse-bugs (14787 mails)

[bugzilla_noreply@xxxxxxxxxx]

https://bugzilla.novell.com/show_bug.cgi?id=221998

           Summary: No NFS locks available: "kernel: lockd/statd: failed to
                    create /var/lib/nfs/sm/<server>: err=-2"
           Product: SUSE Linux 10.1
           Version: Final
          Platform: x86-64
        OS/Version: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Basesystem
        AssignedTo: bnc-team-screening@xxxxxxxxxxxxxxxxxxxxxx
        ReportedBy: Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx
         QAContact: qa@xxxxxxx


When trying to mount NFS filesystems with SLES10, it works, but no locks are
available. That's evident if you try to use "build" on such an NFS-mounted
directory:
initializing rpm db...
warning: waiting for transaction lock on /var/lib/rpm/__db.000
error: can't create transaction lock on /var/lib/rpm/__db.000

The client then has this syslog message:
kernel: lockd/statd: failed to create /var/lib/nfs/sm/<server>: err=-2
kernel: lockd: failed to monitor <server>

Tried Solaris 9 as server: no locks
Tried SLES9 SP3 (i386) as server: mount hangs
Tried SLES10 as server: no locks

As inspired by a bug report that was closed as invalid, I checked the apparmor
profiles, and I found:
(sbin.rpc.statd):
/var/lib/nfs/statd/sm

Please note the two different directories in the profile and in the kernel
message!


-- 
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, or are watching someone who is.