ubuntu-kernel-tests

mkfs.vfat is causing multiple test failures in ubuntu_ltp_syscall on Trusty

Bug #1785198 reported by Po-Hsu Lin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-kernel-tests
Confirmed
Undecided
Unassigned
linux (Ubuntu)
Triaged
Medium
Unassigned
Trusty
New
Undecided
Unassigned

Bug Description

This test failed due to:
    mkfs.vfat: /dev/loop0 contains a mounted filesystem.
    tst_mkfs.c:94: BROK: mkfs.vfat:1: tst_test.c failed with 732

fallocate05 / fsync01 / msync04 / preadv03 / preadv03_64 / pwritev03 / pwrite03_64 / setxattr01 are failing with the same issue.

The mkfs.vfat command only works once for the first test.

So if you run the same test case (e.g. msync04) on a recently rebooted system, it will pass for the first run.

<<<test_start>>>
tag=fallocate05 stime=1533288629
cmdline="fallocate05"
contacts=""
analysis=exit
<<<test_output>>>
tst_device.c:230: INFO: Using test device LTP_DEV='/dev/loop0'
incrementing stop
tst_supported_fs_types.c:72: INFO: Kernel supports ext2
tst_supported_fs_types.c:56: INFO: mkfs.ext2 does exist
tst_supported_fs_types.c:72: INFO: Kernel supports ext3
tst_supported_fs_types.c:56: INFO: mkfs.ext3 does exist
tst_supported_fs_types.c:72: INFO: Kernel supports ext4
tst_supported_fs_types.c:56: INFO: mkfs.ext4 does exist
tst_supported_fs_types.c:72: INFO: Kernel supports xfs
tst_supported_fs_types.c:56: INFO: mkfs.xfs does exist
tst_supported_fs_types.c:72: INFO: Kernel supports btrfs
tst_supported_fs_types.c:52: INFO: mkfs.btrfs does not exist
tst_supported_fs_types.c:72: INFO: Kernel supports vfat
tst_supported_fs_types.c:56: INFO: mkfs.vfat does exist
tst_supported_fs_types.c:95: INFO: Filesystem exfat is not supported
tst_supported_fs_types.c:72: INFO: Kernel supports ntfs
tst_supported_fs_types.c:56: INFO: mkfs.ntfs does exist
tst_test.c:1079: INFO: Testing on ext2
tst_mkfs.c:83: INFO: Formatting /dev/loop0 with ext2 opts='' extra opts=''
mke2fs 1.42.9 (4-Feb-2014)
tst_test.c:1018: INFO: Timeout per run is 0h 05m 00s
fallocate05.c:46: CONF: fallocate() not supported: EOPNOTSUPP
tst_test.c:1079: INFO: Testing on ext3
tst_mkfs.c:83: INFO: Formatting /dev/loop0 with ext3 opts='' extra opts=''
mke2fs 1.42.9 (4-Feb-2014)
tst_test.c:1018: INFO: Timeout per run is 0h 05m 00s
fallocate05.c:46: CONF: fallocate() not supported: EOPNOTSUPP
tst_test.c:1079: INFO: Testing on ext4
tst_mkfs.c:83: INFO: Formatting /dev/loop0 with ext4 opts='' extra opts=''
mke2fs 1.42.9 (4-Feb-2014)
tst_test.c:1018: INFO: Timeout per run is 0h 05m 00s
tst_fill_fs.c:41: INFO: Creating file mntpoint/file0 size 21710183
tst_fill_fs.c:41: INFO: Creating file mntpoint/file1 size 8070086
tst_fill_fs.c:41: INFO: Creating file mntpoint/file2 size 3971177
tst_fill_fs.c:41: INFO: Creating file mntpoint/file3 size 36915315
tst_fill_fs.c:41: INFO: Creating file mntpoint/file4 size 70310993
tst_fill_fs.c:41: INFO: Creating file mntpoint/file5 size 4807935
tst_fill_fs.c:41: INFO: Creating file mntpoint/file6 size 90739786
tst_fill_fs.c:41: INFO: Creating file mntpoint/file7 size 76896492
tst_fill_fs.c:61: INFO: write(): ENOSPC
fallocate05.c:62: PASS: write() wrote 8192 bytes
fallocate05.c:71: PASS: fallocate() on full FS: ENOSPC
fallocate05.c:80: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE)
fallocate05.c:86: PASS: write()
tst_test.c:1079: INFO: Testing on xfs
tst_mkfs.c:83: INFO: Formatting /dev/loop0 with xfs opts='' extra opts=''
tst_test.c:1018: INFO: Timeout per run is 0h 05m 00s
tst_fill_fs.c:41: INFO: Creating file mntpoint/file0 size 21710183
tst_fill_fs.c:41: INFO: Creating file mntpoint/file1 size 8070086
tst_fill_fs.c:41: INFO: Creating file mntpoint/file2 size 3971177
tst_fill_fs.c:41: INFO: Creating file mntpoint/file3 size 36915315
tst_fill_fs.c:41: INFO: Creating file mntpoint/file4 size 70310993
tst_fill_fs.c:41: INFO: Creating file mntpoint/file5 size 4807935
tst_fill_fs.c:41: INFO: Creating file mntpoint/file6 size 90739786
tst_fill_fs.c:41: INFO: Creating file mntpoint/file7 size 76896492
tst_fill_fs.c:61: INFO: write(): ENOSPC
fallocate05.c:62: PASS: write() wrote 8192 bytes
fallocate05.c:71: PASS: fallocate() on full FS: ENOSPC
fallocate05.c:80: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE)
fallocate05.c:86: PASS: write()
tst_test.c:1079: INFO: Testing on vfat
tst_mkfs.c:83: INFO: Formatting /dev/loop0 with vfat opts='' extra opts=''
mkfs.vfat: /dev/loop0 contains a mounted filesystem.
tst_mkfs.c:94: BROK: mkfs.vfat:1: tst_test.c failed with 732

Summary:
passed 8
failed 0
skipped 2
warnings 0
<<<execution_status>>>
initiation_status="ok"
duration=8 termination_type=exited termination_id=2 corefile=no
cutime=6 cstime=105
<<<test_end>>>
INFO: ltp-pan reported some tests FAIL
LTP Version: 20180515

       ###############################################################

            Done executing testcases.
            LTP Version: 20180515
       ###############################################################

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-153-generic 3.13.0-153.203
ProcVersionSignature: User Name 3.13.0-153.203-generic 3.13.11-ckt39
Uname: Linux 3.13.0-153-generic x86_64
AlsaDevices:
 total 0
 crw-rw---- 1 root audio 116, 1 Aug 3 07:50 seq
 crw-rw---- 1 root audio 116, 33 Aug 3 07:50 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.14.1-0ubuntu3.29
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CurrentDmesg:

Date: Fri Aug 3 09:26:34 2018
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
PciMultimedia:

ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-153-generic root=UUID=41f2a2b1-0082-4a56-ad3b-9f99ca574aeb ro
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-153-generic N/A
 linux-backports-modules-3.13.0-153-generic N/A
 linux-firmware 1.127.24
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-xenial
dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-xenial
dmi.sys.vendor: QEMU

See original description
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :
Po-Hsu Lin (cypressyew)
summary: - fallocate05 in ubuntu_ltp_syscall failed with Trusty
+ fallocate05 / fsync01 in ubuntu_ltp_syscall failed with mkfs.vfat error
+ on Trusty
description: updated
summary: - fallocate05 / fsync01 in ubuntu_ltp_syscall failed with mkfs.vfat error
- on Trusty
+ fallocate05 / fsync01 / msync04 in ubuntu_ltp_syscall failed with
+ mkfs.vfat error on Trusty
description: updated
Po-Hsu Lin (cypressyew)
summary: - fallocate05 / fsync01 / msync04 in ubuntu_ltp_syscall failed with
- mkfs.vfat error on Trusty
+ [T] mkfs.vfat is causing failure on fallocate05 / fsync01 / msync04 /
+ preadv03 / pwritev03 / setxattr01 tests in ubuntu_ltp_syscall on Trusty
summary: - [T] mkfs.vfat is causing failure on fallocate05 / fsync01 / msync04 /
+ mkfs.vfat is causing failure on fallocate05 / fsync01 / msync04 /
preadv03 / pwritev03 / setxattr01 tests in ubuntu_ltp_syscall on Trusty
description: updated
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Po-Hsu Lin (cypressyew)
description: updated
Joseph Salisbury (jsalisbury)
Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Triaged
Po-Hsu Lin (cypressyew)
summary: - mkfs.vfat is causing failure on fallocate05 / fsync01 / msync04 /
- preadv03 / pwritev03 / setxattr01 tests in ubuntu_ltp_syscall on Trusty
+ mkfs.vfat is causing failure on fallocate05, fsetxattr01, fgetxattr01,
+ fsync01, msync04, preadv03, preadv03, pwritev03, pwritev03_64,
+ setxattr01 tests in ubuntu_ltp_syscall on Trusty
Revision history for this message
Po-Hsu Lin (cypressyew) wrote : Re: mkfs.vfat is causing failure on fallocate05, fsetxattr01, fgetxattr01, fsync01, msync04, preadv03, preadv03, pwritev03, pwritev03_64, setxattr01 tests in ubuntu_ltp_syscall on Trusty

For AWS T-4.4, the result is a bit different, it's failing with ext2 mkfs.

18:42:24 DEBUG| [stdout] tag=setxattr01 stime=1542048144
18:42:24 DEBUG| [stdout] cmdline="setxattr01"
18:42:24 DEBUG| [stdout] contacts=""
18:42:24 DEBUG| [stdout] analysis=exit
18:42:24 DEBUG| [stdout] <<<test_output>>>
18:42:24 DEBUG| [stdout] tst_device.c:230: INFO: Using test device LTP_DEV='/dev/loop0'
18:42:24 DEBUG| [stdout] tst_supported_fs_types.c:72: INFO: Kernel supports ext2
18:42:24 DEBUG| [stdout] tst_supported_fs_types.c:56: INFO: mkfs.ext2 does exist
18:42:24 DEBUG| [stdout] tst_supported_fs_types.c:72: INFO: Kernel supports ext3
18:42:24 DEBUG| [stdout] tst_supported_fs_types.c:56: INFO: mkfs.ext3 does exist
18:42:24 DEBUG| [stdout] tst_supported_fs_types.c:72: INFO: Kernel supports ext4
18:42:24 DEBUG| [stdout] tst_supported_fs_types.c:56: INFO: mkfs.ext4 does exist
18:42:24 DEBUG| [stdout] tst_supported_fs_types.c:72: INFO: Kernel supports xfs
18:42:24 DEBUG| [stdout] tst_supported_fs_types.c:56: INFO: mkfs.xfs does exist
18:42:24 DEBUG| [stdout] tst_supported_fs_types.c:72: INFO: Kernel supports btrfs
18:42:24 DEBUG| [stdout] tst_supported_fs_types.c:52: INFO: mkfs.btrfs does not exist
18:42:24 DEBUG| [stdout] tst_supported_fs_types.c:72: INFO: Kernel supports vfat
18:42:24 DEBUG| [stdout] tst_supported_fs_types.c:56: INFO: mkfs.vfat does exist
18:42:24 DEBUG| [stdout] tst_supported_fs_types.c:95: INFO: Filesystem exfat is not supported
18:42:24 DEBUG| [stdout] tst_supported_fs_types.c:99: INFO: FUSE does support ntfs
18:42:24 DEBUG| [stdout] tst_supported_fs_types.c:56: INFO: mkfs.ntfs does exist
18:42:24 DEBUG| [stdout] tst_test.c:1146: INFO: Testing on ext2
18:42:24 DEBUG| [stdout] tst_mkfs.c:90: INFO: Formatting /dev/loop0 with ext2 opts='' extra opts=''
18:42:24 DEBUG| [stdout] mke2fs 1.42.9 (4-Feb-2014)
18:42:24 DEBUG| [stdout] /dev/loop0 is mounted; will not make a filesystem here!
18:42:24 DEBUG| [stdout] tst_mkfs.c:101: BROK: mkfs.ext2:1: tst_test.c failed with 749

And there are more failed test cases with these listed above:
lchown03 lchown03_16 linkat02 lchown03 lchown03_16 mknod07 mmap16 mmap16 mount01 mount02 mount03 mount04 mount06 open12 quotactl02 quotactl03 rename11 renameat01 umount01 umount02 umount03 umount2_01 umount2_02 umount2_03 utime06

Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

This is greatly affecting the test process, as it's causing many false alarms, and the failed test cases number are growing.

summary: - mkfs.vfat is causing failure on fallocate05, fsetxattr01, fgetxattr01,
- fsync01, msync04, preadv03, preadv03, pwritev03, pwritev03_64,
- setxattr01 tests in ubuntu_ltp_syscall on Trusty
+ mkfs.vfat is causing multiple test failures in ubuntu_ltp_syscall on
+ Trusty
Changed in ubuntu-kernel-tests:
status: New → Confirmed
importance: Undecided → High
Po-Hsu Lin (cypressyew)
Changed in ubuntu-kernel-tests:
importance: High → Undecided
Po-Hsu Lin (cypressyew)
tags: added: ubuntu-ltp-syscalls
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.