[LU-3575] 'mkfs.lustre --writeconf' not working anymore with Lustre 2.4

• Type: Bug
• Resolution: Duplicate
• Priority: Major
• Affects Version/s: Lustre 2.4.0
• Severity: 3
• Assignee: Alex Zhuravlev
• Reporter: Sebastien Buisson (Inactive)

Description

Hi,

With Lustre 2.4, '--writeconf' flag of mkfs.lustre is ignored. Indeed, after formatting a target with this flag, its label separator is ':', which means VIRGIN, instead of '='.
To force writeconf, one has to run 'tunefs.lustre --writeconf' on the target prior to starting it for the first time.

This is seen as a regression compared to Lustre 2.1, with which we can directly pass the writeconf flag at mkfs.lustre time.

We need this feature (ie forcing writeconf at mkfs time) when we reformat an existing file system registered at an external MGS after modifying its characteristics.

Could it be possible to revise writeconf flag implementation in Lustre 2.4 so that it can be used directly at mkfs.lustre time?

TIA,
Sebastien.

Issue Links

• is related to: LU-14 live replacement of OST

Comments

[Cory Spitz]

If 'mkfs.lustre --writeconf' is flat broke, why didn't we catch this prior to 2.4.0?

[Sebastien Buisson (Inactive)]

Hi there,

I can confirm that this patch (http://review.whamcloud.com/#/c/7232/) solves the problem for me.
Is it possible to also have it on b2_4?

TIA,
Sebastien.

[Patrick Valentin (Inactive)]

Peter, Alex,
Sébastien is out of his office for 2 weeks and will be back on next monday (august 19).
Patrick

[Peter Jones]

Sebastien

Any word as to whether this patch solves the problem for you?

Peter

[Alex Zhuravlev]

Sebastien,
could you try http://review.whamcloud.com/#/c/7232/ please ?

[Jodi Levi (Inactive)]

Alex,
Could you please comment on this one?
Thank you!