[Bug 1211353] New: [Build 20230511] LTP: failure in test statx09
https://bugzilla.suse.com/show_bug.cgi?id=1211353 Bug ID: 1211353 Summary: [Build 20230511] LTP: failure in test statx09 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/3285771/modules/stat x09/steps/8 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs@opensuse.org Reporter: dimstar@opensuse.org QA Contact: qa-bugs@suse.de Target Milestone: --- Found By: openQA Blocker: Yes ## Observation tst_kconfig.c:87: TINFO: Parsing kernel config '/proc/config.gz' tst_cmd.c:285: TINFO: Parsing mkfs.ext4 version tst_device.c:96: TINFO: Found free device 0 '/dev/loop0' tst_test.c:1093: TINFO: Formatting /dev/loop0 with ext4 opts='-O verity' extra opts='' mke2fs 1.46.5 (30-Dec-2021) tst_test.c:1558: TINFO: Timeout per run is 0h 00m 30s statx09.c:108: TBROK: ioctl(3, FS_IOC_ENABLE_VERITY) failed: EINVAL (22) tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 1... tst_device.c:412: TINFO: Likely gvfsd-trash is probing newly mounted fs, kill it to speed up tests. tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 2... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 3... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 4... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 5... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 6... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 7... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 8... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 9... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 10... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 11... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 12... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 13... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 14... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 15... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 16... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 17... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 18... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 19... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 20... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 21... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 22... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 23... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 24... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 25... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 26... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 27... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 28... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 29... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 30... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 31... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 32... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 33... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 34... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 35... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 36... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 37... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 38... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 39... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 40... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 41... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 42... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 43... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 44... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 45... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 46... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 47... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 48... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 49... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 50... tst_device.c:419: TWARN: Failed to umount('mnt_point') after 50 retries Summary: passed 0 failed 0 broken 1 skipped 0 warnings 1 tst_device.c:263: TWARN: ioctl(/dev/loop0, LOOP_CLR_FD, 0) no ENXIO for too long tst_tmpdir.c:342: TWARN: tst_rmdir: rmobj(/tmp/LTP_staCoVZgK) failed: remove(/tmp/LTP_staCoVZgK/mnt_point) failed; errno=16: EBUSY ### TEST statx09 COMPLETE >>> 6. openQA test in scenario opensuse-Tumbleweed-JeOS-for-kvm-and-xen-x86_64-jeos-ltp-syscalls@uefi_virtio-2G fails in [statx09](https://openqa.opensuse.org/tests/3285771/modules/statx09/steps/8) ## Test suite description ## Reproducible Fails since (at least) Build [20230503](https://openqa.opensuse.org/tests/3261645) ## Expected result Last good: [20230502](https://openqa.opensuse.org/tests/3259709) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensuse&flavor=...) -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1211353 https://bugzilla.suse.com/show_bug.cgi?id=1211353#c1 Petr Cervinka <pcervinka@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pcervinka@suse.com Resolution|--- |INVALID Status|NEW |RESOLVED --- Comment #1 from Petr Cervinka <pcervinka@suse.com> --- Ext4 filesystem has blocksize 1024 but statx09 initializes fs-verity with blocksize 4096. Kernel sources require that verity blocksize <= FS blocksize. Martin Doucha did verification https://openqa.opensuse.org/tests/3426555#step/statx09/8. Will be fixed in LTP upstream in few days. -- You are receiving this mail because: You are the assignee for the bug.
participants (1)
-
bugzilla_noreply@suse.com