Details
-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
Lustre 2.4.0
-
None
-
3
-
9043
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.
Attachments
Issue Links
- is related to
-
LU-14 live replacement of OST
- Resolved