Bug#608858: linux-image-2.6.32-bpo.5-amd64: smbd kernel bug copying large file
package linux-2.6 retitle 608858 copying large file with smbd on raid causes BUG at fs/jbd/transaction.c:1156 thanks Gregg gkn...@tampabay.rr.com writes: [1393760.788377] EXT3-fs error (device dm-5): ext3_valid_block_bitmap: Invalid block bitmap - block_group = 1229, block = 40271874 [1393760.788779] [ cut here ] [1393760.788835] kernel BUG at /build/buildd-linux-2.6_2.6.32-28~bpo50+1-i386-VgAojN/linux-2.6-2.6.32/debian/build/source_i386_none/fs/jbd/transaction.c:1156! Sounds like an ext3 bug. Either ext3 corrupted its data structures or something else (HDD, RAM) did and ext3 didn't cope with it. Googling for BUG jbd/transaction.c:1156 finds other cases: I installed Debian Squeeze from a net install to a raid 1 array. I have been having a lot of troubles related to being able to write to one or more of the mounted drives - even touch gives me errors. The most interesting line from dmesg is: [15174.549931] kernel BUG at /tmp/buildd/linux-2.6-2.6.32/debian/build/source_i386_none/fs/jbd/transaction.c:1156! Here is the full output from dmesg: -- http://forums.debian.net/viewtopic.php?f=5t=56527 1) Are you using aacraid on this dm-5 device too? 2) Can you make the bug occur again? 3) If yes, can you temporarily try it without raid at all? (Just make backups before test) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/8462u5jfpm@sauna.l.org
Processed: Re: Bug#608858: linux-image-2.6.32-bpo.5-amd64: smbd kernel bug copying large file
Processing commands for cont...@bugs.debian.org: package linux-2.6 Limiting to bugs with field 'package' containing at least one of 'linux-2.6' Limit currently set to 'package':'linux-2.6' retitle 608858 copying large file with smbd on raid causes BUG at fs/jbd/transaction.c:1156 Bug #608858 [linux-2.6] copying large file with smbd on raid causes BUG at fs/jbd/transaction.c:1156 Ignoring request to change the title of bug#608858 to the same title thanks Stopping processing here. Please contact me if you need assistance. -- 608858: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=608858 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.129422069928810.transcr...@bugs.debian.org
Bug#608858: linux-image-2.6.32-bpo.5-amd64: smbd kernel bug copying large file
package linux-2.6 retitle 608858 copying large file with smbd on raid causes BUG at fs/jbd/transaction.c:1156 thanks [resending via smtp.academica.fi since smtp.netsonic.fi does not seem to be delivering my emails any time soon...] Gregg gkn...@tampabay.rr.com writes: [1393760.788377] EXT3-fs error (device dm-5): ext3_valid_block_bitmap: Invalid block bitmap - block_group = 1229, block = 40271874 [1393760.788779] [ cut here ] [1393760.788835] kernel BUG at /build/buildd-linux-2.6_2.6.32-28~bpo50+1-i386-VgAojN/linux-2.6-2.6.32/debian/build/source_i386_none/fs/jbd/transaction.c:1156! Sounds like an ext3 bug. Either ext3 corrupted its data structures or something else (HDD, RAM) did and ext3 didn't cope with it. Googling for BUG jbd/transaction.c:1156 finds other cases: I installed Debian Squeeze from a net install to a raid 1 array. I have been having a lot of troubles related to being able to write to one or more of the mounted drives - even touch gives me errors. The most interesting line from dmesg is: [15174.549931] kernel BUG at /tmp/buildd/linux-2.6-2.6.32/debian/build/source_i386_none/fs/jbd/transaction.c:1156! Here is the full output from dmesg: -- http://forums.debian.net/viewtopic.php?f=5t=56527 1) Are you using aacraid on this dm-5 device too? 2) Can you make the bug occur again? 3) If yes, can you temporarily try it without raid at all? (Just make backups before test) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/8462u4ibfp@sauna.l.org
Processed: Re: Bug#608858: linux-image-2.6.32-bpo.5-amd64: smbd kernel bug copying large file
Processing commands for cont...@bugs.debian.org: package linux-2.6 Limiting to bugs with field 'package' containing at least one of 'linux-2.6' Limit currently set to 'package':'linux-2.6' retitle 608858 copying large file with smbd on raid causes BUG at fs/jbd/transaction.c:1156 Bug #608858 [linux-2.6] linux-image-2.6.32-bpo.5-amd64: smbd kernel bug copying large file Changed Bug title to 'copying large file with smbd on raid causes BUG at fs/jbd/transaction.c:1156' from 'linux-image-2.6.32-bpo.5-amd64: smbd kernel bug copying large file' thanks Stopping processing here. Please contact me if you need assistance. -- 608858: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=608858 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.12941794501239.transcr...@bugs.debian.org
Bug#608858: linux-image-2.6.32-bpo.5-amd64: smbd kernel bug copying large file
I have not experienced a single bit of trouble until upgrading to this kernel. I will try writing a large file to other file systems as well, but I do know that I can write smaller, 1-300mb, files to other file systems without an issue. Yes I'm using aacraid. I'm using an Adaptec 2820 card with 4 500gb drives in raid 10. This is actually the second time it has happened performing the same action. Copying a large file from a Windows box via the Samba share. I will have to find a spare drive to connect and test. -Original Message- From: Timo Juhani Lindfors [mailto:timo.lindf...@iki.fi] Sent: Tuesday, January 04, 2011 2:22 AM To: Gregg Cc: 608...@bugs.debian.org; cont...@bugs.debian.org Subject: Re: Bug#608858: linux-image-2.6.32-bpo.5-amd64: smbd kernel bug copying large file package linux-2.6 retitle 608858 copying large file with smbd on raid causes BUG at fs/jbd/transaction.c:1156 thanks [resending via smtp.academica.fi since smtp.netsonic.fi does not seem to be delivering my emails any time soon...] Gregg gkn...@tampabay.rr.com writes: [1393760.788377] EXT3-fs error (device dm-5): ext3_valid_block_bitmap: Invalid block bitmap - block_group = 1229, block = 40271874 [1393760.788779] [ cut here ] [1393760.788835] kernel BUG at /build/buildd-linux-2.6_2.6.32-28~bpo50+1-i386-VgAojN/linux-2.6-2.6.32/debia n/build/source_i386_none/fs/jbd/transaction.c:1156! Sounds like an ext3 bug. Either ext3 corrupted its data structures or something else (HDD, RAM) did and ext3 didn't cope with it. Googling for BUG jbd/transaction.c:1156 finds other cases: I installed Debian Squeeze from a net install to a raid 1 array. I have been having a lot of troubles related to being able to write to one or more of the mounted drives - even touch gives me errors. The most interesting line from dmesg is: [15174.549931] kernel BUG at /tmp/buildd/linux-2.6-2.6.32/debian/build/source_i386_none/fs/jbd/transactio n.c:1156! Here is the full output from dmesg: -- http://forums.debian.net/viewtopic.php?f=5t=56527 1) Are you using aacraid on this dm-5 device too? 2) Can you make the bug occur again? 3) If yes, can you temporarily try it without raid at all? (Just make backups before test) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/000c01cbac7f$81f4f6d0$85dee4...@rr.com
Bug#608858: linux-image-2.6.32-bpo.5-amd64: smbd kernel bug copying large file
After forcefully rebooting I have removed VMware from running at boot and will test again. I wanted to make sure nothing was left loaded after just removing the modules. I'm quite experienced in Windows, but don't know the in's and out's of Linux to the extent that I do of Windows. -Original Message- From: Ben Hutchings [mailto:b...@decadent.org.uk] Sent: Tuesday, January 04, 2011 12:03 AM To: Gregg; 608...@bugs.debian.org Subject: Re: Bug#608858: linux-image-2.6.32-bpo.5-amd64: smbd kernel bug copying large file Can you reproduce this without VMware modules loaded? Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/000d01cbac7f$83601f90$8a205e...@rr.com
Bug#608858: linux-image-2.6.32-bpo.5-amd64: smbd kernel bug copying large file
Package: linux-2.6 Version: 2.6.32-29~bpo50+1 Severity: important -- Package-specific info: ** Version: Linux version 2.6.32-bpo.5-amd64 (Debian 2.6.32-28~bpo50+1) (norb...@tretkowski.de) (gcc version 4.3.2 (Debian 4.3.2-1.1) ) #1 SMP Wed Dec 1 21:46:07 UTC 2010 ** Command line: root=UUID=62ff30d3-77c3-4eef-bbd1-231819cb87bb ro ** Tainted: D (128) * Kernel has oopsed before. ** Kernel log: [ 51.333039] /dev/vmnet: port on hub 8 successfully opened [ 51.356845] /dev/vmnet: open called by PID 3306 (vmnet-natd) [ 51.356864] /dev/vmnet: port on hub 8 successfully opened [ 53.700902] cx25840 1-0044: loaded v4l-cx25840.fw firmware (16382 bytes) [ 58.492883] /dev/vmmon[3807]: PTSC: initialized at 1994246000 Hz using TSC [ 58.498766] /dev/vmmon[3807]: Vmx86_InitNUMAInfo : numaNumMemRanges=4 and numaNumNodes=2 [ 59.221035] /dev/vmnet: open called by PID 3810 (vmware-vmx) [ 59.221060] device eth1 entered promiscuous mode [ 59.221190] bridge-eth1: enabled promiscuous mode [ 59.221302] /dev/vmnet: port on hub 0 successfully opened [ 60.718876] /dev/vmnet: open called by PID 3813 (vmnet-netifup) [ 60.718898] /dev/vmnet: port on hub 1 successfully opened [ 61.237004] /dev/vmnet: open called by PID 3831 (vmnet-netifup) [ 61.237027] /dev/vmnet: port on hub 8 successfully opened [1224233.234497] /dev/vmnet: open called by PID 27897 (vmware-vmx) [1224233.234537] /dev/vmnet: port on hub 0 successfully opened [1387784.950567] vmmon: Had to deallocate locked 97788 pages from vm driver 88013f151400 [1387784.957115] vmmon: Had to deallocate AWE 7092 pages from vm driver 88013f151400 [1393758.348153] EXT3-fs error (device dm-5): ext3_valid_block_bitmap: Invalid block bitmap - block_group = 1211, block = 39682050 [1393758.348639] EXT3-fs error (device dm-5): ext3_new_block: Allocating block in system zone - blocks from 39682055, length 1 [1393758.358189] EXT3-fs error (device dm-5): ext3_valid_block_bitmap: Invalid block bitmap - block_group = 1212, block = 39714818 [1393758.358564] EXT3-fs error (device dm-5): ext3_new_block: Allocating block in system zone - blocks from 39714822, length 1 [1393760.652245] EXT3-fs error (device dm-5): ext3_valid_block_bitmap: Invalid block bitmap - block_group = 1213, block = 39747584 [1393760.652848] EXT3-fs error (device dm-5): ext3_new_block: Allocating block in system zone - blocks from 39747584, length 1 [1393760.699782] EXT3-fs error (device dm-5): ext3_valid_block_bitmap: Invalid block bitmap - block_group = 1215, block = 39813122 [1393760.700244] EXT3-fs error (device dm-5): ext3_new_block: Allocating block in system zone - blocks from 39813123, length 1 [1393760.706494] EXT3-fs error (device dm-5): ext3_valid_block_bitmap: Invalid block bitmap - block_group = 1217, block = 39878658 [1393760.706889] EXT3-fs error (device dm-5): ext3_new_block: Allocating block in system zone - blocks from 39878749, length 1 [1393760.714641] EXT3-fs error (device dm-5): ext3_valid_block_bitmap: Invalid block bitmap - block_group = 1218, block = 39911426 [1393760.715014] EXT3-fs error (device dm-5): ext3_new_block: Allocating block in system zone - blocks from 39911613, length 1 [1393760.720552] EXT3-fs error (device dm-5): ext3_valid_block_bitmap: Invalid block bitmap - block_group = 1220, block = 39976961 [1393760.720931] EXT3-fs error (device dm-5): ext3_new_block: Allocating block in system zone - blocks from 39976976, length 1 [1393760.729925] EXT3-fs error (device dm-5): ext3_valid_block_bitmap: Invalid block bitmap - block_group = 1222, block = 40042498 [1393760.730315] EXT3-fs error (device dm-5): ext3_new_block: Allocating block in system zone - blocks from 40042600, length 1 [1393760.735353] EXT3-fs error (device dm-5): ext3_valid_block_bitmap: Invalid block bitmap - block_group = 1223, block = 40075266 [1393760.735726] EXT3-fs error (device dm-5): ext3_new_block: Allocating block in system zone - blocks from 40075267, length 1 [1393760.745867] EXT3-fs error (device dm-5): ext3_valid_block_bitmap: Invalid block bitmap - block_group = 1224, block = 40108033 [1393760.746255] EXT3-fs error (device dm-5): ext3_new_block: Allocating block in system zone - blocks from 40108048, length 1 [1393760.754616] EXT3-fs error (device dm-5): ext3_valid_block_bitmap: Invalid block bitmap - block_group = 1225, block = 40140802 [1393760.755004] EXT3-fs error (device dm-5): ext3_new_block: Allocating block in system zone - blocks from 40140802, length 1 [1393760.761827] EXT3-fs error (device dm-5): ext3_valid_block_bitmap: Invalid block bitmap - block_group = 1226, block = 40173570 [1393760.762284] EXT3-fs error (device dm-5): ext3_new_block: Allocating block in system zone - blocks from 40173672, length 1 [1393760.770746] EXT3-fs error (device dm-5): ext3_valid_block_bitmap: Invalid block bitmap - block_group = 1227, block = 40206338 [1393760.77] EXT3-fs error (device dm-5): ext3_new_block: Allocating block in system zone - blocks from
Bug#608858: linux-image-2.6.32-bpo.5-amd64: smbd kernel bug copying large file
Can you reproduce this without VMware modules loaded? Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
