[LU-13937] Do not return -ENODATA while removing XATTR_NAME_FID Created: 01/Sep/20 Updated: 05/May/21 Resolved: 05/May/21 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | Lustre 2.15.0 |
| Type: | Improvement | Priority: | Major |
| Reporter: | Artem Blagodarenko (Inactive) | Assignee: | Artem Blagodarenko (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | patch | ||
| Rank (Obsolete): | 9223372036854775807 |
| Description |
|
On OST with node size < 256 stripe information is stored in LMA. osd_xattr_set_pfid() expects XATTR_NAME_FID to be exist if LMAC_STRIPE_INF is absent and delete it if LU_XATTR_REPLACE is set. There are some cases, after upgrade, when LMAC_STRIPE_INF is absent and there is no XATTR_NAME_FID. No need return -ENODATA to the client, because having XATTR_NAME_FID absent is what situation requires, so osd_xattr_set_pfid() can continue to feel LMA. |
| Comments |
| Comment by Gerrit Updater [ 01/Sep/20 ] |
|
Artem Blagodarenko (artem.blagodarenko@hpe.com) uploaded a new patch: https://review.whamcloud.com/39790 |
| Comment by Gerrit Updater [ 05/May/21 ] |
|
Oleg Drokin (green@whamcloud.com) merged in patch https://review.whamcloud.com/39790/ |
| Comment by Peter Jones [ 05/May/21 ] |
|
Landed for 2.15 |