fallocate05 in ubuntu_ltp_syscalls failed with ENOSPC on btrfs with 5.10/5.11/5.13
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntu-kernel-tests |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
Issue found on nodes in Intel lab (beoing, vought)
This can be found in 5.10.0-1026-oem as well so this is not a regression
Interesting thing is that this issue cannot be reproduced with a VM, with give a try on our bare-metal node later.
Test log:
tst_test.c:1379: TINFO: Testing on btrfs
tst_test.c:888: TINFO: Formatting /dev/loop3 with btrfs opts='' extra opts=''
tst_test.c:1311: TINFO: Timeout per run is 0h 05m 00s
tst_fill_fs.c:32: TINFO: Creating file mntpoint/file0 size 21710183
tst_fill_fs.c:32: TINFO: Creating file mntpoint/file1 size 8070086
tst_fill_fs.c:32: TINFO: Creating file mntpoint/file2 size 3971177
tst_fill_fs.c:32: TINFO: Creating file mntpoint/file3 size 36915315
tst_fill_fs.c:32: TINFO: Creating file mntpoint/file4 size 70310993
tst_fill_fs.c:32: TINFO: Creating file mntpoint/file5 size 4807935
tst_fill_fs.c:32: TINFO: Creating file mntpoint/file6 size 90739786
tst_fill_fs.c:32: TINFO: Creating file mntpoint/file7 size 76896492
tst_fill_fs.c:32: TINFO: Creating file mntpoint/file8 size 72228649
tst_fill_fs.c:32: TINFO: Creating file mntpoint/file9 size 36207821
tst_fill_fs.c:32: TINFO: Creating file mntpoint/file10 size 81483962
tst_fill_fs.c:32: TINFO: Creating file mntpoint/file11 size 92198827
tst_fill_fs.c:59: TINFO: write(): ENOSPC (28)
fallocate05.c:81: TPASS: write() wrote 65536 bytes
fallocate05.c:102: TINFO: fallocate()d 0 extra blocks on full FS
fallocate05.c:114: TPASS: fallocate() on full FS
fallocate05.c:130: TPASS: fallocate(
fallocate05.c:134: TFAIL: write(): ENOSPC (28)
Please find attachment for the complete test log.
summary: |
- fallocate05 in ubuntu_ltp_syscalls failed with ENOSPC on btrfs with 5.10 - OEM + fallocate05 in ubuntu_ltp_syscalls failed with ENOSPC on btrfs with + 5.10/5.13 OEM |
tags: | added: 5.13 sru-20210719 |
tags: | added: 5.11 azure hirsute sru-20210816 |
Tested with 5.10.0-1026-oem / 5.10.0-1028-oem on node "glameow" in our pool and it does not have this issue.