Uploaded image for project: 'Lustre'
  1. Lustre
  2. LU-1462

Arguments to tunefs/mkfs have an undocumented order dependency

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Low Priority
    • Icon: Minor Minor
    • None
    • Lustre 2.1.0
    • None
    • 3
    • 10365

      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

            wc-triage WC Triage
            john John Spray (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: