[LU-1462] Arguments to tunefs/mkfs have an undocumented order dependency

• Status: Resolved
• Project: Lustre
• Affects Version/s: Lustre 2.1.0
• Type: Bug
• Priority: Minor
• Reporter: John Spray (Inactive)
• Assignee: WC Triage
• Resolution: Low Priority
• Severity: 3

Description

Because of how the arguments to mkfs/tunefs are parsed, these commands are sensitive to the order of arguments. Ideally, --key=value parameters should not be order sensitive. At least, these ordering rules should be documented.

--erase-params

Fails silently if erase-params is not after any param arguments.

This is OK:

tunefs.lustre --erase-params --mgsnode=<new_nid(s)> --writeconf /dev/..

But if we do this, it does not work properly (erase-params deletes the previous mgsnode argument):

tunefs.lustre --mgsnode=<new_nid(s)> --writeconf --erase-params /dev/..

--index

Fails with "--index only valid for MDT,OST" if --index does not come after the target type argument.

This is OK:

tunefs --mdt --index=0

This is not OK:

tunefs --index=0 --mdt

Issue Links

• is related to: LU-2374 the order of --index and --ost should...

Comments

[James Nunez (Inactive)]

LU-2374 fixes the order dependency of --index for mkfs/tunefs in 2.4.2 and 2.5.0