Project

General

Profile

Actions

Bug #4484

closed

lockd: SMF property reading and cli options are incorrect

Added by Youzhong Yang over 7 years ago. Updated over 7 years ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
nfs - NFS server and client
Start date:
2014-01-15
Due date:
% Done:

100%

Estimated time:
Difficulty:
Medium
Tags:
Gerrit CR:

Description

This appears to be an issue with the open source NLM (nfs/lockd+klm). Issue is not reproducible when Sun's proprietary lockd is used.

Here is how to reproduce the issue:

1. On the client (Linux or SmartOS/OmniOS) side, mount a share on the server, make sure there exists a writable file (say /mnt/share/file) on the share.

2. Use the attached perl script, run 'perl locktest.pl 60 /mnt/share/file 10'. It will fork 60 processes, each of which tries to lock the given file repeatedly, for 10 seconds maximum.

I did some dtracing, it seems that 'no lock available' is caused by the thread reservation failure (svc_reserve_thread()):

http://src.illumos.org/source/xref/illumos-gate/usr/src/uts/common/klm/nlm_service.c#543


Files

lockfile.pl (4.51 KB) lockfile.pl Youzhong Yang, 2014-01-15 07:53 PM
Actions

Also available in: Atom PDF