[LU-3087] File layout change does not generate a changelog record Created: 02/Apr/13 Updated: 05/Aug/20 Resolved: 18/Apr/13 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | Lustre 2.4.0 |
| Type: | Bug | Priority: | Minor |
| Reporter: | CEA | Assignee: | Jinshan Xiong (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Severity: | 3 |
| Rank (Obsolete): | 7501 |
| Description |
|
When a file layout is created or changed no changelog record is generated.
|
| Comments |
| Comment by jacques-charles lafoucriere [ 02/Apr/13 ] |
|
We will propose a patch |
| Comment by Peter Jones [ 02/Apr/13 ] |
|
Jinshan I think that you will be the natural person to review this patch when it has been supplied Peter |
| Comment by Alex Zhuravlev [ 03/Apr/13 ] |
|
shouldn't the even for xattr change be enough? |
| Comment by jacques-charles lafoucriere [ 03/Apr/13 ] |
|
The xattr event can be used but it comes from the implementation of lovea and the way it is written on disk. We think a CL_LAYOUT event which matches the "functional" change is better. |
| Comment by Alex Zhuravlev [ 03/Apr/13 ] |
|
strictly speaking, there is no notion of layout in MDD... MDD isn't even aware always of layout change. |
| Comment by Henri Doreau (Inactive) [ 03/Apr/13 ] |
|
Additionally, changelog readers (lustre_rsync or robinhood, typically) may react differently to setxattr and layout changes. This was rather in favor of adding a CL_LAYOUT event. |
| Comment by Alex Zhuravlev [ 03/Apr/13 ] |
|
setxattr(LOVEA) is changing layout by definition, no? |
| Comment by jacques-charles lafoucriere [ 03/Apr/13 ] |
|
yes but it comes from the way lovea is implemented in lustre, this is side effect of implementation not a goal |
| Comment by Alex Zhuravlev [ 03/Apr/13 ] |
|
speaking of goals.. I'd rather say there should be no notion of layout on the server (MDS) - the less details to take care about, the better scalability. |
| Comment by Henri Doreau (Inactive) [ 06/Apr/13 ] |
|
Here's a patch to address the issue: http://review.whamcloud.com/5966 |
| Comment by Peter Jones [ 18/Apr/13 ] |
|
Landed for 2.4 |