Project

General

Profile

Actions

Bug #4965

open

NLM: Mac OS X client can be stuck at locking a NFS file on an illumos server (SmartOS, Nexenta or OmniOS etc.) running open source lockd

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

Status:
New
Priority:
High
Assignee:
-
Category:
nfs - NFS server and client
Start date:
2014-07-07
Due date:
% Done:

0%

Estimated time:
Difficulty:
Tags:
needs-triage
Gerrit CR:

Description

Here is how to reproduce the issue:

Suppose a Mac host has write access to a file /x/y/z located on a illumos nfs server.

- Run the following command to lock and unlock the file, it will succeed

  env FILE=/x/y/z perl -e 'use Fcntl qw(:DEFAULT :flock O_WRONLY LOCK_EX LOCK_UN); my ($fh, $start, $elapsed); if(sysopen ($fh, $ENV{"FILE"}, O_WRONLY)){$start = time; flock($fh, LOCK_EX); flock($fh, LOCK_UN);close $fh; $elapsed = time - $start; print "$elapsed seconds\\\\n";} else {print "ERROR: Could not open file: $!\\\\n";}'

- Reboot the Mac host
- Run the above command again, it will be stuck, spewing lots of 'lockd not responding' message
  nfs server nfs_server_name:nfs_share_path: lockd not responding
  nfs server nfs_server_name:nfs_share_path: lockd not responding
  .
  .
  .

It never ends and you cannot even kill the perl command.

Actions

Also available in: Atom PDF