Details
-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
Lustre 2.12.3
-
None
-
CentOS 7.6
-
3
-
9223372036854775807
Description
During a lfs migrate -m from MDT0002 to MDT0003 of a full directory, we can see a bunch of errors -95:
lfs migrate -m 3 /fir/users/apatel6 ... /fir/users/apatel6/data/600_N_dec_carbons/08-EXX-sensitivity/02-MN4graphene/00-PBE-noNUPDOWN/05-OOH/07-Pd/spincheck/03/01-EXX-10/INCAR migrate failed: Operation not supported (-95)
It seems to be a regular file:
# stat /fir/users/apatel6/data/600_N_dec_carbons/08-EXX-sensitivity/02-MN4graphene/00-PBE-noNUPDOWN/05-OOH/07-Pd/spincheck/03/01-EXX-10/INCAR File: ‘/fir/users/apatel6/data/600_N_dec_carbons/08-EXX-sensitivity/02-MN4graphene/00-PBE-noNUPDOWN/05-OOH/07-Pd/spincheck/03/01-EXX-10/INCAR’ Size: 708 Blocks: 8 IO Block: 4194304 regular file Device: e64e03a8h/3863872424d Inode: 198161414156736433 Links: 1 Access: (0644/-rw-r--r--) Uid: (298250/ apatel6) Gid: (32269/ norskov) Access: 2020-01-17 14:32:11.000000000 -0800 Modify: 2019-08-24 15:41:31.000000000 -0700 Change: 2019-08-24 15:41:31.000000000 -0700 Birth: -
on a regular directory:
# stat /fir/users/apatel6/data/600_N_dec_carbons/08-EXX-sensitivity/02-MN4graphene/00-PBE-noNUPDOWN/05-OOH/07-Pd/spincheck/03/01-EXX-10 File: ‘/fir/users/apatel6/data/600_N_dec_carbons/08-EXX-sensitivity/02-MN4graphene/00-PBE-noNUPDOWN/05-OOH/07-Pd/spincheck/03/01-EXX-10’ Size: 8192 Blocks: 16 IO Block: 4096 directory Device: e64e03a8h/3863872424d Inode: 180147914721584182 Links: 2 Access: (0755/drwxr-xr-x) Uid: (298250/ apatel6) Gid: (32269/ norskov) Access: 2020-02-26 08:32:37.000000000 -0800 Modify: 2019-08-24 19:16:56.000000000 -0700 Change: 2019-08-24 19:16:56.000000000 -0700 Birth: -
so we're wondering why...
Checking the file's parent directory shows that it has been flagged for migration:
# lfs getdirstripe /fir/users/apatel6/data/600_N_dec_carbons/08-EXX-sensitivity/02-MN4graphene/00-PBE-noNUPDOWN/05-OOH/07-Pd/spincheck/03/01-EXX-10
lmv_stripe_count: 2 lmv_stripe_offset: 3 lmv_hash_type: fnv_1a_64,migrating
mdtidx FID[seq:oid:ver]
3 [0x280038894:0xf2d0:0x0]
2 [0x2c002cafe:0xf400:0x0]
The parent of the parent too:
# lfs getdirstripe /fir/users/apatel6/data/600_N_dec_carbons/08-EXX-sensitivity/02-MN4graphene/00-PBE-noNUPDOWN/05-OOH/07-Pd/spincheck/03
lmv_stripe_count: 2 lmv_stripe_offset: 3 lmv_hash_type: fnv_1a_64,migrating
mdtidx FID[seq:oid:ver]
3 [0x280038894:0xf2cd:0x0]
2 [0x2c002cafe:0xd455:0x0]
But the parent of the parent of the parent is already done (is that normal?):
# lfs getdirstripe /fir/users/apatel6/data/600_N_dec_carbons/08-EXX-sensitivity/02-MN4graphene/00-PBE-noNUPDOWN/05-OOH/07-Pd/spincheck lmv_stripe_count: 0 lmv_stripe_offset: 3 lmv_hash_type: none
We have 4 MDTs on this filesystem. We haven't upgraded to 2.12.4 yet but it is planned within the next month.
