kernel BUG at /build/buildd/linux-3.2.0/fs/btrfs/transaction.c:1337!

[Kurt Huwig]

I have btrfs on LVM. When I try to resize the volume with

btrfsctl -r max /var/lib/vmware/iWay

I get a kernel BUG. This is 100% reproducible.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image (not installed)
ProcVersionSignature: Ubuntu 3.2.0-39.62-generic 3.2.39
Uname: Linux 3.2.0-39-generic x86_64
AlsaDevices:
 total 0
 crw-rw---T 1 root audio 116, 1 Apr 4 09:16 seq
 crw-rw---T 1 root audio 116, 33 Apr 4 09:16 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.0.1-0ubuntu17.1
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
Date: Thu Apr 4 09:35:27 2013
HibernationDevice: RESUME=UUID=2c4f34e2-4803-4753-98ae-ac398223c2e2
IwConfig: Error: [Errno 2] No such file or directory
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
MachineType: System manufacturer System Product Name
MarkForUpload: True
PciMultimedia:

ProcEnviron:
 LANGUAGE=en_US:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-39-generic root=/dev/mapper/vg0-root ro nmi_watchdog=0 nomodeset
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-39-generic N/A
 linux-backports-modules-3.2.0-39-generic N/A
 linux-firmware 1.79.1
RfKill: Error: [Errno 2] No such file or directory
SourcePackage: linux
StagingDrivers: mei
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/24/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1008
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8H77-M PRO
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1008:bd01/24/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

[Brad Figg (brad-figg)]

This change was made by a bot.

[Kurt Huwig (k-huwig-f)]

The problem is triggered because the size of the logical volume has been decreased from 700G to 1G (instead of increased to 1T - my fault). Still this should not cause a kernel BUG. After the BUG I was unable to umount the volume or reboot the machine - I had to hard-reset it.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.9 kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.9-rc5-raring/

[Kurt Huwig (k-huwig-f)]

I tested it with

Linux version 3.9.0-030900rc5-generic (apw@gomeisa) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #201303311835 SMP Sun Mar 31 22:36:20 UTC 2013

and a different error appears, this time a BTRFS error with Call Trace.

[Kurt Huwig (k-huwig-f)]

I copied the partition to another machine running quantal. If I mount it read-only, everthing is fine. If I mount it read-write, then the machine crashes with an Oops when unmounting it.

[Kurt Huwig (k-huwig-f)]

I've received a response from a developer that the "BTRFS error" in the upstream kernel is intended behaviour. The kernel BUG in precise and the kernel Oops in quantal are not intended, therefore I've changed the tags from kernel-bug-exists-upstream to kernel-fixed-upstream.