Kernel panic on btrfs mount and ls
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Confirmed
|
High
|
Unassigned | ||
Xenial |
Confirmed
|
High
|
Dragan S. |
Bug Description
Kernel panic happens after mount and ls specific btrfs image
Way to reproduce:
1. download and unpack btrfs image from tar(sparse file)(tar -Sxf img.tar)
2. mount btrfs (sudo mount -t btrfs -o rw,noatime,
3. list files in mount point (ls -al broken)
the system down to kernel panic with log above
(looks like 3.19.x and 4.2.x not affected, only 4.4.x)
dmesg log:
May 31 13:02:21 fs-new kernel: [ 694.744630] BTRFS error (device loop0): parent transid verify failed on 30425088 wanted 120 found 119
May 31 13:02:21 fs-new kernel: [ 694.747077] BTRFS error (device loop0): parent transid verify failed on 30425088 wanted 120 found 119
May 31 13:02:21 fs-new kernel: [ 694.747128] ------------[ cut here ]------------
May 31 13:02:21 fs-new kernel: [ 694.747135] WARNING: CPU: 0 PID: 13795 at /build/
May 31 13:02:21 fs-new kernel: [ 694.747136] ida_remove called for id=47 which is not allocated.
May 31 13:02:21 fs-new kernel: [ 694.747137] Modules linked in: ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c nfsv3 vboxsf xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_
May 31 13:02:21 fs-new kernel: [ 694.747182] CPU: 0 PID: 13795 Comm: ls Tainted: P OE 4.4.0-22-generic #40~14.04.1-Ubuntu
May 31 13:02:21 fs-new kernel: [ 694.747183] Hardware name: innotek GmbH VirtualBox/
May 31 13:02:21 fs-new kernel: [ 694.747185] 0000000000000000 ffff8800024e7a88 ffffffff813cde6c ffff8800024e7ad0
May 31 13:02:21 fs-new kernel: [ 694.747187] ffffffff81af5298 ffff8800024e7ac0 ffffffff8107d856 0000000000000000
May 31 13:02:21 fs-new kernel: [ 694.747189] ffffffff81fce200 ffff88003c827a00 ffff88003616e068 0000000000000001
May 31 13:02:21 fs-new kernel: [ 694.747191] Call Trace:
May 31 13:02:21 fs-new kernel: [ 694.747195] [<ffffffff813cd
May 31 13:02:21 fs-new kernel: [ 694.747199] [<ffffffff8107d
May 31 13:02:21 fs-new kernel: [ 694.747201] [<ffffffff8107d
May 31 13:02:21 fs-new kernel: [ 694.747214] [<ffffffff811a3
May 31 13:02:21 fs-new kernel: [ 694.747217] [<ffffffff813ce
May 31 13:02:21 fs-new kernel: [ 694.747220] [<ffffffff811ff
May 31 13:02:21 fs-new kernel: [ 694.747239] [<ffffffffc00f2
May 31 13:02:21 fs-new kernel: [ 694.747251] [<ffffffffc00f3
May 31 13:02:21 fs-new kernel: [ 694.747264] [<ffffffffc011d
May 31 13:02:21 fs-new kernel: [ 694.747277] [<ffffffffc0106
May 31 13:02:21 fs-new kernel: [ 694.747288] [<ffffffffc0107
May 31 13:02:21 fs-new kernel: [ 694.747291] [<ffffffff81207
May 31 13:02:21 fs-new kernel: [ 694.747293] [<ffffffff81207
May 31 13:02:21 fs-new kernel: [ 694.747295] [<ffffffff81209
May 31 13:02:21 fs-new kernel: [ 694.747297] [<ffffffff8125c
May 31 13:02:21 fs-new kernel: [ 694.747299] [<ffffffff8120a
May 31 13:02:21 fs-new kernel: [ 694.747301] [<ffffffff8120c
May 31 13:02:21 fs-new kernel: [ 694.747304] [<ffffffff811db
May 31 13:02:21 fs-new kernel: [ 694.747306] [<ffffffff8120c
May 31 13:02:21 fs-new kernel: [ 694.747308] [<ffffffff8120c
May 31 13:02:21 fs-new kernel: [ 694.747310] [<ffffffff81202
May 31 13:02:21 fs-new kernel: [ 694.747312] [<ffffffff81202
May 31 13:02:21 fs-new kernel: [ 694.747315] [<ffffffff8121c
May 31 13:02:21 fs-new kernel: [ 694.747317] [<ffffffff81207
May 31 13:02:21 fs-new kernel: [ 694.747318] [<ffffffff81222
May 31 13:02:21 fs-new kernel: [ 694.747321] [<ffffffff81202
May 31 13:02:21 fs-new kernel: [ 694.747324] [<ffffffff817ef
May 31 13:02:21 fs-new kernel: [ 694.747326] ---[ end trace 5c7309d2219a269a ]---
May 31 13:02:21 fs-new kernel: [ 694.761474] Modules linked in: ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c nfsv3 vboxsf xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_
May 31 13:02:21 fs-new kernel: [ 694.763145] CPU: 0 PID: 13581 Comm: zsh Tainted: P W OE 4.4.0-22-generic #40~14.04.1-Ubuntu
May 31 13:02:21 fs-new kernel: [ 694.763207] Hardware name: innotek GmbH VirtualBox/
May 31 13:02:21 fs-new kernel: [ 694.763261] task: ffff880038485280 ti: ffff88001c104000 task.ti: ffff88001c104000
May 31 13:02:21 fs-new kernel: [ 694.763307] RIP: 0010:[<
May 31 13:02:21 fs-new kernel: [ 694.763654] RSP: 0018:ffff88001c
May 31 13:02:21 fs-new kernel: [ 694.763689] RAX: 0000000000000000 RBX: 0000000002000200 RCX: 00000000005306fe
May 31 13:02:21 fs-new kernel: [ 694.763733] RDX: 00000000005306fd RSI: 0000000002000200 RDI: ffff88003c801b00
May 31 13:02:21 fs-new kernel: [ 694.763777] RBP: ffff88001c107d68 R08: 0000000000019f80 R09: ffffffff811bda0d
May 31 13:02:21 fs-new kernel: [ 694.763820] R10: 0000000000000000 R11: ffffffff81ac9018 R12: 0000000002000200
May 31 13:02:21 fs-new kernel: [ 694.763862] R13: 53f000ff53f000ff R14: ffff88003c801b00 R15: ffff88003c801b00
May 31 13:02:21 fs-new kernel: [ 694.763908] FS: 00007f73347c474
May 31 13:02:21 fs-new kernel: [ 694.763958] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
May 31 13:02:21 fs-new kernel: [ 694.763993] CR2: 0000000000ec7ba8 CR3: 0000000002445000 CR4: 00000000000406f0
May 31 13:02:21 fs-new kernel: [ 694.764043] Stack:
May 31 13:02:21 fs-new kernel: [ 694.764059] ffffffff81fc7220 ffff88001c0807d0 ffff880002440380 0000000000000000
May 31 13:02:21 fs-new kernel: [ 694.764113] 0000000000000001 ffff880035ea3a98 ffff88001c107dc0 ffffffff811bda0d
May 31 13:02:21 fs-new kernel: [ 694.764166] ffff88000241e4b0 ffff88001c080848 ffff88000241e528 0000000000000000
May 31 13:02:21 fs-new kernel: [ 694.764219] Call Trace:
May 31 13:02:21 fs-new kernel: [ 694.764243] [<ffffffff811bd
May 31 13:02:21 fs-new kernel: [ 694.764280] [<ffffffff811bd
May 31 13:02:21 fs-new kernel: [ 694.766727] [<ffffffff8107b
May 31 13:02:21 fs-new kernel: [ 694.767979] [<ffffffff8107c
May 31 13:02:21 fs-new kernel: [ 694.771206] [<ffffffff8108c
May 31 13:02:21 fs-new kernel: [ 694.774372] [<ffffffff8107c
May 31 13:02:21 fs-new kernel: [ 694.775874] [<ffffffff817ef
May 31 13:02:21 fs-new kernel: [ 694.776895] Code: 4c 03 05 83 e6 e2 7e 4d 8b 28 49 8b 40 10 4d 85 ed 0f 84 43 01 00 00 48 85 c0 0f 84 3a 01 00 00 49 63 46 20 48 8d 4a 01 4d 8b 06 <49> 8b 5c 05 00 4c 89 e8 65 49 0f c7 08 0f 94 c0 84 c0 74 b8 49
May 31 13:02:21 fs-new kernel: [ 694.779447] RIP [<ffffffff811db
May 31 13:02:21 fs-new kernel: [ 694.780143] RSP <ffff88001c107d38>
May 31 13:02:21 fs-new kernel: [ 694.780965] fbcon_switch: detected unhandled fb_set_par error, error code -16
May 31 13:02:21 fs-new kernel: [ 694.782726] fbcon_switch: detected unhandled fb_set_par error, error code -16
May 31 13:02:21 fs-new kernel: [ 694.784621] ---[ end trace 5c7309d2219a269b ]---
Kernel: Ubuntu 4.4.0-22.
Release: Description: Ubuntu 14.04.3 LTS, Release: 14.04
Btrfs-tools version:
Installed: 3.12-1
Candidate: 3.12-1ubuntu0.1
Version table:
3.
500 http://
*** 3.12-1 0
500 http://
100 /var/lib/
---
AlsaDevices:
total 0
crw-rw---- 1 root audio 116, 1 May 31 13:46 seq
crw-rw---- 1 root audio 116, 33 May 31 13:46 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=
InstallationDate: Installed on 2015-09-28 (246 days ago)
InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
IwConfig: Error: [Errno 2] No such file or directory
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99
MachineType: innotek GmbH VirtualBox
NonfreeKernelMo
Package: linux (not installed)
PciMultimedia:
ProcFB: 0 vboxdrmfb
ProcKernelCmdLine: BOOT_IMAGE=
ProcVersionSign
RelatedPackageV
linux-
linux-
linux-firmware 1.127.14
RfKill: Error: [Errno 2] No such file or directory
Tags: trusty
Uname: Linux 4.4.0-22-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: dmi:bvninnotekG
dmi.product.name: VirtualBox
dmi.product.
dmi.sys.vendor: innotek GmbH
Changed in linux (Ubuntu Xenial): | |
assignee: | nobody → Dragan S. (dragan-s) |
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
apport-collect 1587475
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.