https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 https://jira.whamcloud.com/browse/LU-4294 Lustre <p>I deactivate an OST with</p> <p>lctl --device 56 deactivate</p> <p>56 being the first column number of "lctl dl" output.</p> <p>After this "lctl dl" still shows the OST as "UP":</p> <p>56 UP osp vegas-OST0059-osc-MDT0000 vegas-MDT0000-mdtlov_UUID 5</p> <p>Doing a</p> <p>cat /proc/fs/lustre/lov/vegas-MDT0000-mdtlov/target_obd</p> <p>however shows the OST set to INACTIVE:</p> <p>89: vegas-OST0059_UUID INACTIVE</p> Lustre 2.4.1 RHEL6 2.6.32-358.18.1.el6_lustre.x86_64 LU-4294

lctl dl does not show inactive state for deactivated OST

Bug Minor Resolved Duplicate Emoly Liu Wolfgang Baudler server Fri, 22 Nov 2013 13:53:07 +0000 Fri, 18 Apr 2014 02:38:03 +0000 Fri, 18 Apr 2014 02:38:03 +0000 Lustre 2.4.1 0 7 <p>"UP" means the device is configured, it is not the same thing as INACTIVE.</p> <p>This seems to have changed between Lustre 1.8 and Lustre 2.x: With Lustre 1.8 "lctl dl" reported "IN".<br/> Therefore, the question is if this change was intended since it might confuse administrators (like me). <br/> Also, if the change was intended the Lustre 2.x manual has to be adapted, e.g. chapter 18.8.3 and chapter 19.1.2.</p> <p>Emoly</p> <p>Could you please look into this one?</p> <p>Thanks</p> <p>Peter</p> <p>I have a check at Lustre 2.x manual and find it does say "lctl dl" reports "IN". But I think the example should be older than b2_4, because since b2_4 OSP has been added to replace OSC connected from MDS.</p> <p>The following values are part of "lctl dl" from b2_3 and master branch respectively.</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>b2_3: 10 UP mdc lustre-MDT0000-mdc-ffff88003c798000 aff4df3d-483c-c37a-bed4-19f17dd103ed 5 11 UP osc lustre-OST0000-osc-ffff88003c798000 aff4df3d-483c-c37a-bed4-19f17dd103ed 5 12 UP osc lustre-OST0001-osc-ffff88003c798000 aff4df3d-483c-c37a-bed4-19f17dd103ed 5 13 UP osc lustre-OST0000-osc-MDT0000 lustre-MDT0000-mdtlov_UUID 5 14 UP osc lustre-OST0001-osc-MDT0000 lustre-MDT0000-mdtlov_UUID 5 </pre> </div></div> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>master: 18 UP mdc lustre-MDT0000-mdc-ffff88002379b800 67d79455-bc1e-4856-d567-68656b793b34 5 19 UP osc lustre-OST0000-osc-ffff88002379b800 67d79455-bc1e-4856-d567-68656b793b34 5 20 UP osc lustre-OST0001-osc-ffff88002379b800 67d79455-bc1e-4856-d567-68656b793b34 5 21 UP osp lustre-OST0000-osc-MDT0000 lustre-MDT0000-mdtlov_UUID 5 22 UP osp lustre-OST0001-osc-MDT0000 lustre-MDT0000-mdtlov_UUID 5 </pre> </div></div> <p>And the code shows that although OSP can receive de/activated setting by "lctl --device", osp_import_event() doesn't call obd_notify() to update obd_inactive status used by "lctl dl". That's why we didn't see "IN" change by deactivating osp device.</p> <p>Since "lctl dl" output has changed in newer Lustre versions this should be reflected in the Lustre 2.x manual. Can you create a documentation bug?</p> <p>Yes, <a href="https://jira.whamcloud.com/browse/LUDOC-218" title="update Lustre 2.x manual to reflect OSP changes in &quot;lctl dl&quot; output" class="issue-link" data-issue-key="LUDOC-218">LUDOC-218</a> is created for doc update.</p> <p>Do I understand correctly that this issue is essentially a duplicate of <a href="https://jira.whamcloud.com/browse/LUDOC-218" title="update Lustre 2.x manual to reflect OSP changes in &quot;lctl dl&quot; output" class="issue-link" data-issue-key="LUDOC-218">LUDOC-218</a>?</p> <p>Yes, this issue can be marked as a duplicate of <a href="https://jira.whamcloud.com/browse/LUDOC-218" title="update Lustre 2.x manual to reflect OSP changes in &quot;lctl dl&quot; output" class="issue-link" data-issue-key="LUDOC-218">LUDOC-218</a>. And in the future if needed, we can file a new ticket to modify OSP code.</p> Related LUDOC-218 Development Epic server Rank 1|hzw9xb: Rank (Obsolete) 11778 Severity