[LU-6535] updating fsname and index wth different orders have problems Created: 28/Apr/15  Updated: 05/Jun/15  Resolved: 05/Jun/15

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: None
Fix Version/s: Lustre 2.8.0

Type: Bug Priority: Minor
Reporter: Wang Shilong (Inactive) Assignee: Emoly Liu
Resolution: Fixed Votes: 0
Labels: patch

Severity: 3
Rank (Obsolete): 9223372036854775807

 Description   

Updating fsname with following command failed:
tunefs.lustre --fsname lustre --writeconf /dev/mgs

But using following command succeed:
tunefs.lustre --writeconf --fsname lustre /dev/mgs

IT turned out this is because of options parsing order,
but actually, we should let both two ways work, so fix is also simple to
do sanity check after we have parsed all options.



 Comments   
Comment by Gerrit Updater [ 28/Apr/15 ]

Shilong Wang (wshilong@ddn.com) uploaded a new patch: http://review.whamcloud.com/14632
Subject: LU-6535 utils: fix updating index and fsname
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: ca2855f078ca1277a2e64520fa8cec249acc13ef

Comment by Peter Jones [ 28/Apr/15 ]

Emoly

Can you please take care of this patch?

Thanks

Peter

Comment by Gerrit Updater [ 05/Jun/15 ]

Oleg Drokin (oleg.drokin@intel.com) merged in patch http://review.whamcloud.com/14632/
Subject: LU-6535 utils: fix updating index and fsname
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: c735a3ef9780fe846292b1f4a11d4cc47d90d5e7

Comment by Peter Jones [ 05/Jun/15 ]

Landed for 2.8

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