[LU-9173] OST label tokenizer changes from = to - after first mount Created: 02/Mar/17  Updated: 22/Dec/17  Resolved: 22/Dec/17

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: Lustre 2.4.3, Lustre 2.5.5
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Jessica Otey Assignee: WC Triage
Resolution: Not a Bug Votes: 0
Labels: None
Environment:

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.


Severity: 3
Rank (Obsolete): 9223372036854775807

 Description   

This is similar to LU-3167, but in this case the change is between an equal sign and a dash.

The issue can be triggered either by attempting to mount a newly-created volume by label, or an existing volume after a writeconf.

Once the volume is mounted for the first time, after an unmount, it can be remounted successfully using the dash in the label.

This behavior may be common to Lustre 2.x.



 Comments   
Comment by Andreas Dilger [ 03/Mar/17 ]

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.

Besides the change in the label, is this actually causing some problem?

Generated at Sat Feb 10 02:23:52 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.