[LUDOC-219] Permanent deactivating an OST does survive after reboot Created: 24/Jan/14 Updated: 15/Sep/16 |
|
| Status: | Open |
| Project: | Lustre Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor |
| Reporter: | Zhiqi Tao (Inactive) | Assignee: | Lustre Manual Triage |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Environment: |
Lustre 2.3/IEEL 1.0 |
||
| Severity: | 3 |
| Rank (Obsolete): | 12397 |
| Description |
|
As described in http://build.whamcloud.com/job/lustre-manual/lastSuccessfulBuild/artifact/lustre_manual.xhtml 14.8.3. Removing an OST from the File System 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 However, after reboot, the OST would become active "UP" again while it should be always inactive "IN". |