mkfs01_ext3_sh, mkfs01_ext4_sh failed on Eoan

[Po-Hsu Lin]

Issue found on node amaura (5.3.0-29-generic)

<<<test_start>>>
tag=mkfs01_ext3_sh stime=1581489860
cmdline="mkfs01.sh -f ext3"
contacts=""
analysis=exit
<<<test_output>>>
mkfs01 1 TINFO: timeout per run is 0h 5m 0s
tst_device.c:244: INFO: Using test device LTP_DEV='/dev/loop3'
mkfs01 1 TPASS: 'mkfs -t ext3 /dev/loop3 ' passed.
mkfs01 2 TFAIL: 'mkfs -t ext3 /dev/loop3 16000' failed, not expected.
mkfs01 3 TPASS: 'mkfs -t ext3 -c /dev/loop3 ' passed.
mkfs01 4 TPASS: 'mkfs -V ' passed.
mkfs01 5 TPASS: 'mkfs -h ' passed.
mkfs01 6 TINFO: AppArmor enabled, this may affect test results
mkfs01 6 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires super/root)
mkfs01 6 TINFO: loaded AppArmor profiles: none

Summary:
passed 4
failed 1
skipped 0
warnings 0
<<<execution_status>>>
initiation_status="ok"
duration=2 termination_type=exited termination_id=1 corefile=no
cutime=8 cstime=11
<<<test_end>>>
<<<test_start>>>
tag=mkfs01_ext4_sh stime=1581489862
cmdline="mkfs01.sh -f ext4"
contacts=""
analysis=exit
<<<test_output>>>
incrementing stop
mkfs01 1 TINFO: timeout per run is 0h 5m 0s
tst_device.c:244: INFO: Using test device LTP_DEV='/dev/loop3'
tst_device.c:281: INFO: Skipping $LTP_DEV size 0MB, requested size 256MB
tst_device.c:87: INFO: Found free device 3 '/dev/loop3'
mkfs01 1 TPASS: 'mkfs -t ext4 /dev/loop3 ' passed.
mkfs01 2 TFAIL: 'mkfs -t ext4 /dev/loop3 16000' failed, not expected.
mkfs01 3 TPASS: 'mkfs -t ext4 -c /dev/loop3 ' passed.
mkfs01 4 TPASS: 'mkfs -V ' passed.
mkfs01 5 TPASS: 'mkfs -h ' passed.
mkfs01 6 TINFO: AppArmor enabled, this may affect test results
mkfs01 6 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires super/root)
mkfs01 6 TINFO: loaded AppArmor profiles: none

Summary:
passed 4
failed 1
skipped 0
warnings 0
<<<execution_status>>>
initiation_status="ok"
duration=1 termination_type=exited termination_id=1 corefile=no
cutime=4 cstime=13
<<<test_end>>>

Nothing special from dmesg:
[ 996.969998] LTP: starting mkfs01_ext3_sh (mkfs01.sh -f ext3)
[ 998.274638] EXT4-fs (loop3): mounting ext3 file system using the ext4 subsystem
[ 998.275580] EXT4-fs (loop3): mounted filesystem with ordered data mode. Opts: (null)
[ 998.839778] LTP: starting mkfs01_ext4_sh (mkfs01.sh -f ext4)
[ 1000.060363] EXT4-fs (loop3): mounted filesystem with ordered data mode. Opts: (null)

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: linux-image-5.3.0-29-generic 5.3.0-29.31
ProcVersionSignature: User Name 5.3.0-29.31-generic 5.3.13
Uname: Linux 5.3.0-29-generic x86_64
AlsaDevices:
 total 0
 crw-rw---- 1 root audio 116, 1 Feb 12 06:27 seq
 crw-rw---- 1 root audio 116, 33 Feb 12 06:27 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CurrentDmesg:
 [ 996.969998] LTP: starting mkfs01_ext3_sh (mkfs01.sh -f ext3)
 [ 998.274638] EXT4-fs (loop3): mounting ext3 file system using the ext4 subsystem
 [ 998.275580] EXT4-fs (loop3): mounted filesystem with ordered data mode. Opts: (null)
 [ 998.839778] LTP: starting mkfs01_ext4_sh (mkfs01.sh -f ext4)
 [ 1000.060363] EXT4-fs (loop3): mounted filesystem with ordered data mode. Opts: (null)
Date: Wed Feb 12 06:45:22 2020
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
MachineType: Intel Corporation S1200RP
PciMultimedia:

ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=C.UTF-8
 SHELL=/bin/bash
ProcFB: 0 mgag200drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro
RelatedPackageVersions:
 linux-restricted-modules-5.3.0-29-generic N/A
 linux-backports-modules-5.3.0-29-generic N/A
 linux-firmware 1.183.3
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/01/2015
dmi.bios.vendor: Intel Corp.
dmi.bios.version: S1200RP.86B.03.02.0003.070120151022
dmi.board.asset.tag: ....................
dmi.board.name: S1200RP
dmi.board.vendor: Intel Corporation
dmi.board.version: G62254-407
dmi.chassis.asset.tag: ....................
dmi.chassis.type: 17
dmi.chassis.vendor: ..............................
dmi.chassis.version: ..................
dmi.modalias: dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr....................:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..............................:ct17:cvr..................:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: S1200RP
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: ....................
dmi.sys.vendor: Intel Corporation

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1862889

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.