From aea405208570b6a20a7fef3a475f675d1c2811a5 Mon Sep 17 00:00:00 2001 From: Vladislav Bolkhovitin Date: Wed, 13 Jul 2016 23:24:41 +0000 Subject: [PATCH] README.dlm update to refer to LVB truncation prevention patch git-svn-id: http://svn.code.sf.net/p/scst/svn/trunk@6909 d57e44dd-8a1f-0410-8b47-8ef2f437770f --- scst/README.dlm | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/scst/README.dlm b/scst/README.dlm index 435e6d8bb..7abe92849 100644 --- a/scst/README.dlm +++ b/scst/README.dlm @@ -13,6 +13,7 @@ with a DLM lock object is called the Lock Value Block or LVB. The code in scst_dlm.c uses the DLM to keep PR data synchronized across all nodes in a cluster. + Software Components ------------------- @@ -29,6 +30,11 @@ The following software components are needed by the code in scst_dlm.c: On most Linux distributions the software packages that contain this software have the names kernel, dlm, corosync and pacemaker. +NOTE! You might need to apply a DLM bugfix patch, see scst-devel mailing list +thread https://sourceforge.net/p/scst/mailman/scst-devel/thread/CADHfD59FK6seaammL8b9LM3U3tw5HvYp3kPTk_r1OYkPR7bPhg@mail.gmail.com/#msg34761854 +for more details. + + DLM Configuration ----------------- @@ -74,6 +80,7 @@ configure and start the DLM control daemon: 12. Check the Pacemaker status: pcs status + Startup and Shutdown -------------------- @@ -127,6 +134,7 @@ The proper shutdown order is as follows: * Unload the SCST kernel modules * Unload the DLM kernel driver + Lockspace names --------------- @@ -134,12 +142,14 @@ The names of the DLM lockspaces used by SCST follow the following pattern: scst- where t10_dev_id is the T10 device ID of the SCST device associated with this lockspace. + Notes ----- Since the lockspace name depends on the t10_dev_id it is not allowed to change the t10_dev_id if cluster mode has been enabled. + Testing ------- @@ -148,12 +158,14 @@ Two examples of test suites for the cluster PR support code are: * The Windows Cluster Validation Tests (https://technet.microsoft.com/en-us/library/Cc726064.aspx). + To do ----- Ensure that PREEMPT AND ABORT affects all cluster nodes instead of only the cluster node that received this command. + See also --------