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-9173 Lustre <p>This is similar to <a href="https://jira.whamcloud.com/browse/LU-3167" title="The MDT volume label tokenizer is not consistent" class="issue-link" data-issue-key="LU-3167"><del>LU-3167</del></a>, but in this case the change is between an equal sign and a dash.</p> <p>The issue can be triggered either by attempting to mount a newly-created volume by label, or an existing volume after a writeconf.</p> <p>Once the volume is mounted for the first time, after an unmount, it can be remounted successfully using the dash in the label.</p> <p>This behavior may be common to Lustre 2.x.</p> RHEL 6.8; both our lustre filesytems began at RHEL 5 Lustre 1.8.x and were upgraded from 1.8.9 to (RHEL 6) Lustre 2.4.3. LU-9173

OST label tokenizer changes from = to - after first mount

Bug Minor Resolved Not a Bug WC Triage Jessica Otey Thu, 2 Mar 2017 16:19:57 +0000 Fri, 22 Dec 2017 04:30:10 +0000 Fri, 22 Dec 2017 04:30:10 +0000 Lustre 2.4.3 Lustre 2.5.5 0 3 <p>This change in the label is intentional, and is used as a method of tracking whether the target has ever been configured with the MGS or not.</p> <p>Besides the change in the label, is this actually causing some problem?</p> Development Rank 1|hzz5nb: Rank (Obsolete) 9223372036854775807 Severity