Details
-
Bug
-
Resolution: Fixed
-
Minor
-
Lustre 2.14.0, Lustre 2.16.1
-
None
-
3
-
9223372036854775807
Description
It appears that if "lfs_migrate FILE" is run without specifying an OST pool, then the existing pool that a file is allocated on is lost, due to a bug in the script. Running the "lfs migrate" command without any arguments does not lose the pool, but if some other argument is passed (e.g. "-c 2") then the OST pool in the layout is also lost.
This can cause file objects to be allocated on the wrong OSTs during a mass migration.