From: Andreas Dilger Date: Thu, 4 Aug 2016 23:17:54 +0000 (-0600) Subject: LUDOC-342 maintenance: fix error activating an OSC X-Git-Tag: 2.9.0~9 X-Git-Url: https://git.whamcloud.com/?a=commitdiff_plain;h=e53f9a41cf658c4131162c87279c7380715f0634;p=doc%2Fmanual.git LUDOC-342 maintenance: fix error activating an OSC Fix error in reactivating a temporarily-deactivated OSC. It incorrectly used "active=0" instead of "active=1" when reactivating the OSC device. Signed-off-by: Andreas Dilger Change-Id: I127db4fcb5ccc2bd8dba84ba53e0d8d47a256cad Reviewed-on: http://review.whamcloud.com/21733 Tested-by: Jenkins Reviewed-by: Joseph Gmitter --- diff --git a/LustreMaintenance.xml b/LustreMaintenance.xml index cdad1b6..4ce9c39 100644 --- a/LustreMaintenance.xml +++ b/LustreMaintenance.xml @@ -384,7 +384,8 @@ Removing and Restoring OSTs If the MDT is permanently inaccessible, lfs rmdir {directory} can be used to delete the directory entry. A normal rmdir will report an IO error due to the remote MDT being inactive. After the remote directory has been removed, the administrator should mark the MDT as permanently inactive with: lctl conf_param {MDT name}.mdc.active=0 -A user can identify the location of a remote sub-directory using the lfs utility. For example: +A user can identify which MDT holds a remote sub-directory using +the lfs utility. For example: client$ lfs getstripe -M /mnt/lustre/remote_dir1 1 client$ mkdir /mnt/lustre/local_dir0 @@ -471,21 +472,26 @@ client$ lfs getstripe -M /mnt/lustre/local_dir0 Deactivate the OST. - To temporarily disable the deactivated OST, enter: - [client]# lctl set_param osc.fsname-OSTnumber-*.active=0If - there is expected to be a replacement OST in some short time (a few days), the OST - can temporarily be deactivated on the clients: - This setting is only temporary and will be reset if the clients or MDS are - rebooted. It needs to be run on all clients. + + If there is expected to be a replacement OST in some short + time (a few days), the OST can temporarily be deactivated on + the clients using: + client# lctl set_param osc.fsname-OSTnumber-*.active=0 + This setting is only temporary and will be reset + if the clients are remounted or rebooted. It needs to be run + on all clients. - If there is not expected to be a replacement for this OST in the near future, - permanently deactivate the OST on all clients and the MDS: - [mgs]# lctl conf_param ost_name.osc.active=0 + If there is not expected to be a replacement for this OST in + the near future, permanently deactivate it on all clients and the MDS + by running the following command on the MGS: + mgs# lctl conf_param ost_name.osc.active=0 - A removed OST still appears in the file system; do not create a new OST with the - same name. + A deactivated OST still appears in the file system + configuration, though a new OST with the same name can be + created using the --replace option for + mkfs.lustre. @@ -583,13 +589,14 @@ oss0# dd if=/tmp/ldd of=/mnt/ost/CONFIGS/mountdata bs=4 count=1 seek=5 skip=5 co <indexterm> <primary>maintenance</primary> <secondary>reintroducing an OSTs</secondary> - </indexterm> Returning a Deactivated OST to Service - If the OST was permanently deactivated, it needs to be reactivated in the MGS - configuration. - mgs# lctl conf_param ost_name.osc.active=1 If - the OST was temporarily deactivated, it needs to be reactivated on the MDS and clients. + Returning a Deactivated OST to Service + If the OST was permanently deactivated, it needs to be + reactivated in the MGS configuration. + mgs# lctl conf_param ost_name.osc.active=1 + If the OST was temporarily deactivated, it needs to be reactivated on + the MDS and clients. mds# lctl --device lustre_devno activate - client# lctl set_param osc.fsname-OSTnumber-*.active=0 +client# lctl set_param osc.fsname-OSTnumber-*.active=1
@@ -610,8 +617,8 @@ Determining Which Machine is Serving an OST as such, LNET does not use IP addresses as node identifiers, but NIDs instead. To identify the NID that is serving a specific OST, run one of the following commands on a client (you do not need to be a root user): - client$ lctl get_param osc.fsname-OSTnumber*.ost_conn_uuidFor - example: + client$ lctl get_param osc.fsname-OSTnumber*.ost_conn_uuid + For example: client$ lctl get_param osc.*-OST0000*.ost_conn_uuid osc.testfs-OST0000-osc-f1579000.ost_conn_uuid=192.168.20.1@tcp- OR -