From 207fbec5262efa1ef46d200abc3cb9bf6d1be0f5 Mon Sep 17 00:00:00 2001 From: pschwan Date: Tue, 4 Feb 2003 19:34:19 +0000 Subject: [PATCH] - Do the LOCK_CHANGED work in ldlm_lock_enqueue inside an ns_lock; it was making me nervous without. - The lock may have already received a blocking AST, while it was still owned by the server. In this case, the client will receive the lock, oblivious to the fact that it needs to be given up. Unset the "AST already sent" flag before handing the lock to the client. - Add mdc_sem calls around ldlm_cli_enqueue in mdc_request --- lustre/tests/rename.pl | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lustre/tests/rename.pl b/lustre/tests/rename.pl index 241a201..3ba9368 100644 --- a/lustre/tests/rename.pl +++ b/lustre/tests/rename.pl @@ -5,7 +5,7 @@ use Getopt::Long; sub usage () { print "Usage: $0 \n"; - print "example: $0 --count=2 /mnt/lustre 2 50\n"; + print "example: $0 --count=2 /mnt/lustre 50\n"; print " will test in /mnt/lustre1 and /mnt/lustre2\n"; print " $0 --count=0 /mnt/lustre 50\n"; print " will test in /mnt/lustre only\n"; -- 1.8.3.1