From 208ce54e98b2eabacddc8e7f34b5b39733f97a20 Mon Sep 17 00:00:00 2001 From: dlavigne Date: Fri, 5 Feb 2016 08:40:21 -0500 Subject: [PATCH] Clarify description for deactivatepool. --- api/classes/iocage.rst | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/api/classes/iocage.rst b/api/classes/iocage.rst index 81d79f1..ff20263 100644 --- a/api/classes/iocage.rst +++ b/api/classes/iocage.rst @@ -914,7 +914,9 @@ These examples show responses when the pool is not specified: Deactivate a Pool ================= -The "deactivatepool" action can be used to prevent jail creation on the specified ZFS pool. +Since only one pool can be active, the "deactivatepool" action can be used to deactivate a currently active pool. This should be done before using the +"activatepool" action to activate a different pool. When a pool is deactivated, no data is removed. However, you won't have access to its jails unless you move those datasets to the newly +activated pool or activate the old pool again. **REST Request**