[LU-11784] PFL layouts can exceed EA size limits Created: 14/Dec/18 Updated: 07/Mar/20 Resolved: 07/Mar/20 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor |
| Reporter: | Patrick Farrell (Inactive) | Assignee: | Patrick Farrell (Inactive) |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | PFL2 | ||
| Issue Links: |
|
||||||||
| Severity: | 3 | ||||||||
| Rank (Obsolete): | 9223372036854775807 | ||||||||
| Description |
|
The current code for limiting layout sizes is not fully updated for PFL. In particular, some of the limits use LOV_MAX_STRIPE_COUNT and the size of a stripe to fix the maximum layout size. This breaks down with multiple components. The overstriping feature in This ticket is to work out what the actual current limit on EA size is (there are several different ones documented in the code, and Lustre crashes below all of them) and update the layout code to not allow creation of layouts that exceed it. |
| Comments |
| Comment by Andreas Dilger [ 27/Jun/19 ] |
|
Patrick, is this ticket still needed, or were the "large xattr" issues mostly addressed? Are we sticking with the "2000 stripe" maximum (about 48KB for plain RAID-0 layouts), or do we want to bite the bullet and allow a layout that is closer to the 64KB xattr size limit (possibly reserving some space so that the whole MDS reply can still fit into a 64KB buffer)? That would give us closer to 2500-2600 stripes, maybe 2560 stripes = 61504 bytes reasonable maximum to shoot for, leaving 4032 bytes for other parts of the RPC. Not that this is an urgent issue to pay attention to, just trying to close the ticket if it isn't needed. |
| Comment by Andreas Dilger [ 07/Mar/20 ] |
|
I think this was resolved with |