search for: __journal_remove_journal_head

...ed when this happens (no heavy file/disk io). Any insights or patches that I can try? (i searched lkml and ext3 lists but could not find any similar oops/reports). == Oops =================== BUG: unable to handle kernel NULL pointer dereference at 0000000000000008 IP: [<ffffffff80373520>] __journal_remove_journal_head+0x10/0x120 PGD 0 Oops: 0000 [#1] SMP last sysfs file: /sys/class/scsi_host/host0/proc_name CPU 0 Pid: 3834, comm: kjournald Not tainted 2.6.30.1_test #1 RIP: 0010:[<ffffffff80373520>] [<ffffffff80373520>] __journal_remove_journal_head+0x10/0x120 RSP: 0018:ffff880c7ee11d80 EFLAGS: 0001...

...systems replayed the journal successfully. Relevant log entries leading up to the oops: Nov 4 04:54:08 localhost kernel: attempt to access beyond end of device Nov 4 04:54:08 localhost kernel: 03:02: rw=1, want=401891121, limit=102312 Nov 4 04:54:08 localhost kernel: Assertion failure in __journal_remove_journal_head() at journal.c:1634: "buffer_jbd(bh)" The filesystem in question is the root filesystem. The taint was caused by the openprom module, which was the only module loaded. Please let me know if you need any further data. Regards, Sean. ksymoops 2.4.3 on sparc64 2.4.13-pre6. Opt...

...c351dda0 c351d260 cbc28c00 cbc28540 d882c260 c05e8ce0 da0c0180 da0c06c0 Call Trace: [<c01614c3>] [<c01e93d3>] [<c0164375>] [<c01641e0>] [<c0105726>] [<c0164200>] Code: 8b 56 04 85 d2 79 23 68 c7 fd 22 c0 68 bc 06 00 00 68 19 fb >>EIP; c0165e69 <__journal_remove_journal_head+9/e0> <===== Trace; c01614c3 <journal_commit_transaction+343/119a> Trace; c01e93d3 <ip_rcv+313/3a0> Trace; c0164375 <kjournald+175/2b0> Trace; c01641e0 <commit_timeout+0/10> Trace; c0105726 <kernel_thread+26/30> Trace; c0164200 <kjournald+0/2b0> Code; c0...

...nel: attempt to access beyond end of device Sep 25 10:46:51 gw kernel: 09:03: rw=1, want=1912610820, limit=4192192 Sep 25 10:46:51 gw kernel: attempt to access beyond end of device Sep 25 10:46:51 gw kernel: 09:03: rw=1, want=536870916, limit=4192192 Sep 25 10:46:51 gw kernel: Assertion failure in __journal_remove_journal_head() at journal.c:1730: "buffer_jbd(bh)" ksymoops: Error (expand_objects): cannot stat(/lib/ext3.o) for ext3 ksymoops: No such file or directory Error (expand_objects): cannot stat(/lib/jbd.o) for jbd ksymoops: No such file or directory Warning (compare_maps): mismatch on symbol partition_n...

...rence at virtual address 00000004 ^M printing eip: ^Mc01fab35 ^M*pgd = c040fa1800000000 ^M*pmd = 0000000000000000 ^MOops: 0000 [#1] ^MSMP ^MCPU: 2 ^MEIP: 0060:[<c01fab35>] Not tainted VLI ^MEFLAGS: 00010246 (2.6.10-grsec+gg3+e+fhs6b+nfs+gr0501+++p4+c4a+gr6b-reslog-v6.189) ^MEIP is at __journal_remove_journal_head+0x9/0x130 ^Meax: 00000000 ebx: 00000000 ecx: f7d4f200 edx: 00000014 ^Mesi: f1920320 edi: 00000013 ebp: c0d6f280 esp: f46d5dcc ^Mds: 007b es: 007b ss: 0068 ^MProcess kjournald (pid: 1091, threadinfo=f46d4000 task=f597ca60) ^MStack: f1920320 da3ee14c c01fac83 f1920320 f1920320 c01f70f...

...): ext3_journal_start_sb: Detected aborted journal May 6 06:22:28 srv1a kernel: ext3_abort called. May 6 06:22:28 srv1a kernel: EXT3-fs error (device drbd0): ext3_journal_start_sb: Detected aborted journal May 6 06:22:28 srv1a kernel: Remounting filesystem read-only May 6 06:22:28 srv1a kernel: __journal_remove_journal_head: freeing b_committed_data May 6 06:22:28 srv1a kernel: __journal_remove_journal_head: freeing b_committed_data May 6 06:22:28 srv1a kernel: __journal_remove_journal_head: freeing b_committed_data May 6 06:22:28 srv1a kernel: journal commit I/O error May 6 06:22:28 srv1a kernel: EXT3-fs error (d...

...0 stams kernel: EXT3-fs error (device sda1) in start_transaction: Journal has aborted Dec 7 05:59:51 stams kernel: EXT3-fs error (device sda1) in ext3_ordered_writepage: IO failure Dec 7 05:59:54 stams sshd(pam_unix)[25816]: session opened for user root by (uid=0) Dec 7 05:59:55 stams kernel: __journal_remove_journal_head: freeing b_committed_data Dec 7 05:59:59 stams last message repeated 5 times Dec 7 05:59:59 stams kernel: __journal_remove_journal_head: freeing b_frozen_data Dec 7 05:59:59 stams last message repeated 5 times Dec 7 05:59:59 stams kernel: __journal_remove_journal_head: freeing b_committed_da...

..., name_len=78 Aborting journal on device dm-4. ext3_abort called. EXT3-fs error (device dm-4): ext3_journal_start_sb: Detected aborted journal Remounting filesystem read-only EXT3-fs error (device dm-4) in start_transaction: Journal has aborted EXT3-fs error (device dm-4) in ext3_create: IO failure __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data

...c_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0 Aborting journal on device sda1. EXT3-fs error (device sda1) in ext3_ordered_writepage: IO failure ext3_abort called. EXT3-fs error (device sda1): ext3_journal_start_sb: Detected aborted journal Remounting filesystem read-only __journal_remove_journal_head: freeing b_frozen_data __journal_remove_journal_head: freeing b_frozen_data EXT3-fs error (device sda1): ext3_readdir: bad entry in directory #11: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0 EXT3-fs error (device sda1): ext3_readdir: bad entry in directory #11: rec_le...

...know how I might go about debugging this? As I said, the only thing that has changed recently (the last four months) is the removal of the old mirrored drives and then the addition of these two new drives. Thanks in advance for any help. Here is the error message in full: Assertion failure in __journal_remove_journal_head() at journal.c:1772: "buffer_jbd(bh)" ------------[ cut here ]------------ kernel BUG at journal.c:1772! invalid operand: 0000 nfsd lockd sunrpc autofs tulip ide-cd cdrom usb-uhci usbcore ext3 jbd raid1 CPU: 0 EIP: 0010:[<e0818b59>] Not tainted EFLAGS: 00010282 EIP is at __journ...

...: aborting transaction: Journal has aborted in __ext3_journal_get_write_access<2>EXT3-fs error (device sdb1) in ext3_reserve_inode_write: Journal has aborted EXT3-fs error (device sdb1) in ext3_orphan_del: Journal has aborted EXT3-fs error (device sdb1) in ext3_truncate: Journal has aborted __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data ext3_abort called. EXT3-fs abort (device sdb1): ext3_journal_start: Detected aborted journal Remounting filesystem read-only EXT3-fs error (device sdb1) in start_transaction: Journal has aborted

While doing this on an 80gig ibm ide drive: dd if=/dev/cdrom of=cd.iso I got the following assertian failure Aug 9 14:43:27 budder kernel: Assertion failure in __journal_remove_journal_head() at journal.c:1733: "jh2bh(jh) == bh" Aug 9 14:43:27 budder kernel: kernel BUG at journal.c:1733! Aug 9 14:43:27 budder kernel: invalid operand: 0000 Aug 9 14:43:27 budder kernel: CPU: 0 Aug 9 14:43:27 budder kernel: EIP: 0010:[<c01635a4>] Tainted: P Aug 9 14:43:27 budder...

I've been trying to use fsck to recover a corrupted filesystem. It appears the original superblock is corrupted too, as it has an inode count of 0. When I start fsck with -b 32760, it uses the alternate superblock and proceeds. However, it restarts from the beginning a couple of times and after the second restart it doesn't use the alternate superblock, stopping instead as it can't

...3-fs (xvda2): error: ext3_journal_start_sb: Detected aborted journal [1215379.304200] EXT3-fs (xvda2): error: remounting filesystem read-only [1215379.329043] EXT3-fs (xvda2): error: remounting filesystem read-only [1215379.329246] EXT3-fs (xvda2): error in ext3_create: IO failure [1215379.330502] __journal_remove_journal_head: freeing b_committed_data After shuting down of domUs, fsck failed to repair the filesystem and restore of files was necessary. No updates of XEN or the kernel were made the days before. It was no possible to reproduce the problem yet. Setup for both physical hosts is exactly the same: dom0 --...

...error on device sdg1, logical block 151945219 Nov 9 01:15:15 kasse kernel: lost page write due to I/O error on sdg1 Nov 9 01:15:15 kasse kernel: scsi12 (0:0): rejecting I/O to offline device Nov 9 01:15:15 kasse kernel: scsi12 (0:0): rejecting I/O to offline device Nov 9 01:15:15 kasse kernel: __journal_remove_journal_head: freeing b_committed_data Nov 9 01:15:15 kasse kernel: scsi12 (0:0): rejecting I/O to offline device Nov 9 01:15:15 kasse kernel: scsi12 (0:0): rejecting I/O to offline device Nov 9 01:15:15 kasse kernel: usb 1-1.1: USB disconnect, address 13 Nov 9 01:15:15 kasse kernel: scsi12 (0:0): rejectin...

...ernel: EXT3-fs error (device dm-3) in ext3_orphan_del: Journal has aborted Jul 17 09:01:07 kernel: EXT3-fs error (device dm-3) in ext3_reserve_inode_write: Journal has aborted Jul 17 09:01:07 kernel: EXT3-fs error (device dm-3) in ext3_delete_inode: Journal has aborted Jul 17 09:01:07 kernel: __journal_remove_journal_head: freeing b_committed_data If I run fsck it does seem to repair bad blocks and clears inodes but of course for 8TB it takes a long time to run and the corruption only comes back later. I have considered upgrading the kernel, it could be done. I think part of the problem is the large num...

..._blocks_sb: aborting transaction: Journal has aborted in __ext3_journal_get_undo_access<2>EXT3-fs error (device sdb1) in ext3_free_blocks_sb: Journal has aborted ... Feb 16 10:12:10 hera kernel: EXT3-fs error (device sdb1) in ext3_delete_inode: Journal has aborted Feb 16 10:12:10 hera kernel: __journal_remove_journal_head: freeing b_committed_data Feb 16 10:12:10 hera last message repeated 5 times Feb 16 10:12:10 hera kernel: ext3_abort called. Feb 16 10:12:10 hera kernel: EXT3-fs error (device sdb1): ext3_journal_start_sb: Detected aborted journal Feb 16 10:12:10 hera kernel: Remounting filesystem read-only My be...

...lock bitmap - block_group =3D 1086, block_bitmap =3D 35586048 [ 38.907956] Aborting journal on device dm-0. [ 38.919742] ext3_abort called. [ 38.919798] EXT3-fs error (device dm-0): ext3_journal_start_sb: = Detected aborted journal [ 38.919942] Remounting filesystem read-only [ 38.925855] __journal_remove_journal_head: freeing b_committed_data [ 38.925915] journal commit I/O error [ 38.925935] journal commit I/O error [ 38.925953] journal commit I/O error [ 38.943245] Remounting filesystem read-only [ 38.958907] EXT3-fs error (device dm-0) in ext3_reserve_inode_write: = Journal has aborted [ 38.95898...

Hi, At the time of writing this mail, a few days ago, I couldn''t access the lists, so my apologies if this mail is received duplicate. I recently bought a new server with a 3Ware 8006-2LP controller to run Xen on a Debian linux distribution: - Server: ASUS RS120-E4/PA4 - Debian Release: etch - Architecture: 32bit / 686 - Memory: 8 GB - Disks: 2x Hitachi HDT725050VLA360 - Controller:

...node_write: Journal has aborted [11266.342839] EXT3-fs error (device hda) in ext3_reserve_inode_write: Journal has aborted [11266.351870] EXT3-fs error (device hda) in ext3_orphan_del: Journal has aborted [11266.360540] EXT3-fs error (device hda) in ext3_truncate: Journal has aborted [11266.412056] __journal_remove_journal_head: freeing b_committed_data [11266.421834] ext3_abort called. [11266.425341] EXT3-fs error (device hda): ext3_journal_start_sb: Detected aborted journal [11266.433776] Remounting filesystem read-only [11269.300117] md: stopping all md devices. [11269.304244] md: md0 switched to read-only mode. [11280...