[LU-14286] fallocate() does not zero on-disk data Created: 01/Jan/21 Updated: 30/Jan/21 Resolved: 27/Jan/21 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.14.0 |
| Fix Version/s: | Lustre 2.14.0 |
| Type: | Bug | Priority: | Blocker |
| Reporter: | Arshad Hussain | Assignee: | Arshad Hussain |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||||||||||||||
| Severity: | 3 | ||||||||||||||||||||
| Rank (Obsolete): | 9223372036854775807 | ||||||||||||||||||||
| Description |
|
The ldiskfs osd_fallocate() does not correctly zero the allocated blocks. This is not noticed during autotest and local developer testing because the underlying storage is zero-filled due to using a sparse backing file and will usually read back as zero. Also, the fsx data correctness test was not properly detecting fallocate() support, and as a result this behavior was not detected until after fsx was fixed. fsx uses test_fallocate() to determine if fallocate() along with its various FLAGS is enabled and could be called. This was discovered while working on |
| Comments |
| Comment by Gerrit Updater [ 01/Jan/21 ] |
|
Arshad Hussain (arshad.hussain@aeoncomputing.com) uploaded a new patch: https://review.whamcloud.com/41119 |
| Comment by Andreas Dilger [ 10/Jan/21 ] |
|
Arshad, I've recharacterized this ticket to be more about the osd_fallocate() bug rather than the fsx bug, since it is essentially a data corruption issue that needs to be fixed as part of 2.14.0, and since this patch was already fixing the problem. Rather than spin up a new patch with the same fix, I instead changed the commit message to make it clear the importance of the patch and the reason that it is being included in 2.14.0 at this late date. |
| Comment by Gerrit Updater [ 11/Jan/21 ] |
|
Oleg Drokin (green@whamcloud.com) merged in patch https://review.whamcloud.com/41119/ |
| Comment by Peter Jones [ 11/Jan/21 ] |
|
Landed for 2.14 |
| Comment by Gerrit Updater [ 12/Jan/21 ] |
|
Andreas Dilger (adilger@whamcloud.com) uploaded a new patch: https://review.whamcloud.com/41204 |
| Comment by Andreas Dilger [ 12/Jan/21 ] |
|
Still not fixed. |
| Comment by Gerrit Updater [ 12/Jan/21 ] |
|
James Nunez (jnunez@whamcloud.com) uploaded a new patch: https://review.whamcloud.com/41211 |
| Comment by Gerrit Updater [ 13/Jan/21 ] |
|
Andreas Dilger (adilger@whamcloud.com) merged in patch https://review.whamcloud.com/41211/ |
| Comment by Gerrit Updater [ 13/Jan/21 ] |
|
Alex Zhuravlev (bzzz@whamcloud.com) uploaded a new patch: https://review.whamcloud.com/41216 |
| Comment by Gerrit Updater [ 22/Jan/21 ] |
|
Oleg Drokin (green@whamcloud.com) merged in patch https://review.whamcloud.com/41216/ |
| Comment by Gerrit Updater [ 25/Jan/21 ] |
|
Oleg Drokin (green@whamcloud.com) merged in patch https://review.whamcloud.com/41204/ |
| Comment by Gerrit Updater [ 25/Jan/21 ] |
|
Andreas Dilger (adilger@whamcloud.com) uploaded a new patch: https://review.whamcloud.com/41315 |
| Comment by Gerrit Updater [ 27/Jan/21 ] |
|
Oleg Drokin (green@whamcloud.com) merged in patch https://review.whamcloud.com/41315/ |
| Comment by Peter Jones [ 27/Jan/21 ] |
|
Finally I think that everything tracked here has landed |