When 'destroy-namespace' or 'create-namespace --reconfig' operations
encounter a namespace that is mounted, the operation will always fail.
The '--force' option only forces continuation when the namespace is
active and not mounted. If the namespace is mounted then even --force
will fail.

Reported-by: Jeff Balk <jeff.b...@intel.com>
Signed-off-by: Dan Williams <dan.j.willi...@intel.com>
---
 Documentation/ndctl/ndctl-create-namespace.txt  |   11 +++++++----
 Documentation/ndctl/ndctl-destroy-namespace.txt |    5 ++++-
 2 files changed, 11 insertions(+), 5 deletions(-)

diff --git a/Documentation/ndctl/ndctl-create-namespace.txt 
b/Documentation/ndctl/ndctl-create-namespace.txt
index 85d1f8db792f..4f1f9849207f 100644
--- a/Documentation/ndctl/ndctl-create-namespace.txt
+++ b/Documentation/ndctl/ndctl-create-namespace.txt
@@ -133,10 +133,13 @@ OPTIONS
 
 -f::
 --force::
-       Unless this option is specified a 'reconfigure
-       namespace' operation will fail if the namespace is presently
-       active.  Specifying --force causes the namespace to be disabled
-       before reconfiguring.
+       Unless this option is specified the 'reconfigure namespace'
+       operation will fail if the namespace is presently active.
+       Specifying --force causes the namespace to be disabled before
+       the operation is attempted. However, if the namespace is
+       mounted then the 'disable namespace' and 'reconfigure
+       namespace' operations will be aborted.  The namespace must be
+       unmounted before being reconfigured.
 
 -v::
 --verbose::
diff --git a/Documentation/ndctl/ndctl-destroy-namespace.txt 
b/Documentation/ndctl/ndctl-destroy-namespace.txt
index 8130b2156452..7078c0b21929 100644
--- a/Documentation/ndctl/ndctl-destroy-namespace.txt
+++ b/Documentation/ndctl/ndctl-destroy-namespace.txt
@@ -20,7 +20,10 @@ include::xable-namespace-options.txt[]
        Unless this option is specified the 'destroy namespace'
        operation will fail if the namespace is presently active.
        Specifying --force causes the namespace to be disabled before
-       the operation is attempted.
+       the operation is attempted. However, if the namespace is
+       mounted then the 'disable namespace' and 'destroy
+       namespace' operations will be aborted.  The namespace must be
+       unmounted before being destroyed.
 
 COPYRIGHT
 ---------

_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm

Reply via email to