From 49d9b53380e7d58d1dc3b00c8d949839559d9da1 Mon Sep 17 00:00:00 2001 From: Joseph Gmitter Date: Wed, 21 Sep 2016 10:22:58 -0400 Subject: [PATCH] LUDOC-337 fix: flock example should mount using mgs not mds The mount command example should mount using mgs@tcp instead of mds@tcp. Also, a minor style issue is fixed with the example. Signed-off-by: Joseph Gmitter Change-Id: I01d94aad640adebd239005ef14d18e6de8a25a8a Reviewed-on: https://review.whamcloud.com/22658 Tested-by: Jenkins --- SystemConfigurationUtilities.xml | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git a/SystemConfigurationUtilities.xml b/SystemConfigurationUtilities.xml index d9e7d59..d748e46 100644 --- a/SystemConfigurationUtilities.xml +++ b/SystemConfigurationUtilities.xml @@ -2707,12 +2707,18 @@ lr_reader - A call to use flock may be blocked if another process is holding an incompatible lock. Locks created using flock are applicable for an open file table entry. Therefore, a single process may hold only one type of lock (shared or exclusive) on a single file. Subsequent flock calls on a file that is already locked converts the existing lock to the new lock mode. + A call to use flock may be blocked if another process is holding an + incompatible lock. Locks created using flock are applicable for an + open file table entry. Therefore, a single process may hold only one + type of lock (shared or exclusive) on a single file. Subsequent flock + calls on a file that is already locked converts the existing lock to + the new lock mode.
Example - $ mount -t lustre -o flock mds@tcp0:/lustre /mnt/client + $ mount -t lustre -o flock mgs@tcp0:/lustre /mnt/client You can check it in /etc/mtab. It should look like, - mds@tcp0:/lustre /mnt/client lustre rw,flock 0 0 + mgs@tcp0:/lustre /mnt/client lustre rw,flock 0 0 +
-- 1.8.3.1