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
