[LU-338] Lustre client reports wrong file size (zero, or too small) on first stat Created: 17/May/11 Updated: 21/Sep/11 Resolved: 24/May/11 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 1.8.6 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor |
| Reporter: | Christopher Morrone | Assignee: | Niu Yawei (Inactive) |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Environment: |
1.8.5.0-3chaos, RHEL5.5ish (CHAOS4.4-2) |
||
| Severity: | 3 |
| Rank (Obsolete): | 10167 |
| Description |
|
I'm getting reports that lustre is reporting the wrong file size on the first stat (that they know of) after file creation. This seems to be relatively rare, and difficult to reproduce, but is happening at least a few times a week site wide that we know about. The reports are a bit fuzzy so far, and I am trying to get more useful info out of folks. Often on the first stat, a file's size will be reported as zero. They claim that occasionally it will be a "power of 2", but smaller than the actual file size. I didn't get a more specific number than that yet. The claim is that the file creation and stats happened on the same client node. (Note that our filesystem default stripe count is 2.) I wish that I had better info than that. I will continue to try to get more information. But I seem to remember that Oak Ridge may have seen the same issue, so I wanted to get a tracker open. |
| Comments |
| Comment by Andreas Dilger [ 17/May/11 ] |
|
I suspect from the description that this is a duplicate of |
| Comment by Peter Jones [ 18/May/11 ] |
|
Niu Could you please confirm whether this is a duplicate of LU274? Thanks Peter |
| Comment by Niu Yawei (Inactive) [ 18/May/11 ] |
|
It probably be a duplicated of |
| Comment by Christopher Morrone [ 18/May/11 ] |
|
Ah, yes, that does sound like the likely culprit, thanks! You can mark this a duplicate of |
| Comment by Peter Jones [ 24/May/11 ] |
|
Duplicate of LU274 |
| Comment by Prakash Surya (Inactive) [ 21/Sep/11 ] |
|
We have received a report of this issue happening again since applying |
| Comment by Niu Yawei (Inactive) [ 21/Sep/11 ] |
|
I'm afraid that if the problem is caused by another rare race in size glimpse ( |