[lustre-discuss] Question on why mdt.*.migrate_hsm_allowed is not set to 1 by default
Wang, Huaqing
huaqing at amazon.com
Fri Jan 26 10:07:39 PST 2024
Hello,
We noticed Operation not supported (95) error returned when “lfs migrate” command being run on a directory including files which have been hsm archived to S3 on a 2.15 lustre file system with multiple MDS (DNE)
# lfs mkdir -i 0 testdir
# cd testdir/
# echo "123" > a.txt
# lfs hsm_archive a.txt
# cd ..
# lfs migrate -m 1 testdir
lfs migrate: testdir/a.txt migrate failed: Operation not supported (95)
Once we enable migrate_hsm_allowed, we don’t see errors/issues anymore.
# lctl get_param mdt.*.migrate_hsm_allowed
mdt.abcdefg-MDT0001.migrate_hsm_allowed=0
# lctl set_param mdt.*.migrate_hsm_allowed=1
mdt.abcdefg-MDT0001.migrate_hsm_allowed=1
My question is why we don’t set migrate_hsm_allowed to 1 as default value and is there concern we should know if we choose to set that to 1? Thanks!
Please let me know if I can provide any more information.
Thanks,
Huaqing Wang
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lustre.org/pipermail/lustre-discuss-lustre.org/attachments/20240126/ffc27fa4/attachment-0001.htm>
More information about the lustre-discuss
mailing list