[LU-11510] preserve PFL/FLR/DoM layout with lfs_migrate

• Type: Bug
• Resolution: Fixed
• Priority: Minor
• Fix Version/s: Lustre 2.14.0, Lustre 2.12.5
• Affects Version/s: Lustre 2.11.0, Lustre 2.12.0
• Severity: 3
• Assignee: Emoly Liu
• Reporter: Andreas Dilger

Description

The lfs_migrate tool does not currently preserve the PFL/FLR/DoM components of the layout when a file is migrated. By default, it will get the stripe_count and stripe_size of the file (maybe pool and mirror_count if https://review.whamcloud.com/32977 is updated to do so), but it does not preserve more complex layout details.

Dropping the initial components of a PFL file is probably desirable, since it is unlikely that a file will become smaller, and it makes sense to keep the stripe_count of a file at the widest needed.

We do need to keep the number of mirrors across migration, and it would probably be good to keep any OST pools per mirror, if they exist.

Separately, it would be useful to have some way to migrate only the mirror(s) that exist on particular OSTs if we are trying to empty particular OSTs.

Issue Links

• is related to: LU-18903 interop sanity test_230c: FAIL: mkdir failed under migrating directory
• is related to: LU-13703 fix lfs_migrate to work with PFL arguments
• is related to: LU-13683 lfs migrate on non-existing file returns exit code 0
• is related to: LU-9629 lfs migrate does not work as a non-root user
• is related to: LU-10801 argument parsing in lfs_migrate is broken
• is related to: LU-9392 lfs migrate -o and lfs setstripe -o should pick OST from ost_list
• is related to: LU-9982 Clients striping from mapped FID in nodemap