search for: b_committed_data

...debugging, and here's the output: buffer trace for buffer at 0xc02db000 (I am CPU 0) journal_dirty_metadata() [transaction.c:1101] file as BJ_Metadata b_state:0xb1 b_list:BUF_CLEAN b_jlist:BJ_Metadata on_lru:1 cpu:0 on_hash:1 b_count:2 b_blocknr:1 b_jbd:1 b_frozen_data:00000000 b_committed_data:00000000 b_transaction:1 b_next_transaction:0 b_cp_transaction:0 b_trans_is_running:1 b_trans_is_comitting:0 b_jcount:0 <0> journal_dirty_metadata() [transaction.c:1106] exit b_state:0xb1 b_list:BUF_CLEAN b_jlist:BJ_Metadata on_lru:1 cpu:0 on_hash:1 b_count:2 b_blocknr:1...

...ted 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 (device drbd0): htree_dirblo...

This patch adds jbd_lock_bh_state() and jbd_unlock_bh_state() around accessses to jh->b_committed_data. Fixes oss bugzilla#1131 http://oss.oracle.com/bugzilla/show_bug.cgi?id=1131 Signed-off-by: Sunil Mushran <sunil.mushran at oracle.com> --- fs/ocfs2/suballoc.c | 28 ++++++++++++++++++++++++---- 1 files changed, 24 insertions(+), 4 deletions(-) diff --git a/fs/ocfs2/suballoc.c b/fs/ocfs...

...e 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

Hey, I've a problem with an ext3 filesystem and don't know how to fix it or find the failure :( The Hardware: Tyan mainboard, AMD Athlon CPU, ARECA ARC-1120 RaidController Raid5 with 400GB Seagate HD's, 756 MB Ram, other harddisks for system, network and avm isdn controller. Couse of the filesystem problems I run memtest and found one bad memory module which I replaced yet. The

...ext3 on a Linux for S/390 with several stress and benchmark test tests and faced a kernel bug message. The console showed the following output: Message from syslogd@boeaet34 at Fri Aug 3 11:34:16 2001 ... boeaet34 kernel: Assertion failure in journal_forget() at transaction.c:1184: "! jh->b_committed_data" I tried the Patch from http://www.zip.com.au/~akpm/ext3-2.4-0.9.5-247.gz with the kernel 2.4.7 with a new LVM- patch(0.9.1) and some S/390 specific patches. I use mke2fs version 1.22. S/390 is a 32bit big endian machine. After compiling and running the kernel I created an ext3-file system o...

...(handle,bh); 62 } 63 return bh; --- 5. Error reported in ext3/balloc.c --- CID: 3545 Checker: CHECKED_RETURN File: fs/ext3/balloc.c Function: ext3_free_blocks_sb Description: Return value of "test_and_set_bit" is not checked 439 BUFFER_TRACE(bitmap_bh, "set in b_committed_data"); 440 J_ASSERT_BH(bitmap_bh, 441 bh2jh(bitmap_bh)->b_committed_data != NULL); Event check_return: Called function "test_and_set_bit" whose return value should be checked (checked 83 out of 95 times) Event unchecked_value: Return value of "test_...

...rted 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

...a1) 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_data Dec 7 05:59:59 stams ke...

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

.../jlbec/ocfs2.git upstream-linus Jan Kara (2): vfs: Set special lockdep map for dirs only if not set by fs ocfs2: Add lockdep annotations Joel Becker (1): ocfs2: Provide the ocfs2_dlm_lvb_valid() stack API. Sunil Mushran (5): ocfs2: Pin journal head before accessing jh->b_committed_data ocfs2: Fix ocfs2_osb_dump() ocfs2: Stop orphan scan as early as possible during umount ocfs2: Do not initialize lvb in ocfs2_orphan_scan_lock_res_init() ocfs2: Disable orphan scanning for local and hard-ro mounts Tao Ma (2): ocfs2: Update atime in splice read if neces...

Hi, I found the following in the logs of a server that crashed: Mar 19 14:09:28 sc4 kernel: Assertion failure in ext3_free_blocks() at balloc.c line 358: "bh->b_committed_data != NULL" Mar 19 14:09:28 sc4 kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000000 Mar 19 14:09:28 sc4 kernel: current->tss.cr3 = 39b8b000, %%cr3 = 39b8b000 Mar 19 14:09:28 sc4 kernel: *pde = 00000000 Mar 19 14:09:28 sc4 kernel: Oops: 0002 Mar 19 14:09:28 sc4...

My system had the following error sent to syslog: kernel: Assertion failure in ext3_free_blocks() at balloc.c line 358: "bh->b_committed_data != NULL" Immediately before that with the same timestamp was a sendmail entry. The system locked up shortly after that. I never saw an oops. I was tailing /var/log/messages in a terminal. That syslog entry was not saved to disk. I have not been able to repeat that error. Slackware 8.0 2...

..._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 ----- Debian GNU/Linux 7.5...

I recently rebooted one of my machines and was greeted with a message about one of my ext3 partitions having some errors. I dutifully started e2fsck on the partition, but after a few hours of some useful messages about fixing inodes, it then started printing out lists of ascending numbers which I'm not sure how to interpret. The first time I noticed this, these numbers were in the 4000000

...945219 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): rejecting I/O to device being remo...

...blocks in system zones - Block = 573501, count = 2 Dec 1 22:17:55 pollux kernel: EXT3-fs error (device md(9,11)): ext3_free_blocks : Freeing blocks in system zones - Block = 573552, count = 14 Dec 1 22:17:55 pollux kernel: Assertion failure in journal_forget() at transaction.c:1225: "!jh->b_committed_data" Trying to access the partition resulted in processes hanging in D state: 5336 pts/0 D 0:00 ls -a -N --color=tty -T 0 -l /mnt/data8 e2fstools version is 1.32 and the partition was created with this version using 'mke2fs -j -b 2048 -i 4096 -R stride=16 /dev/md11'. An earli...

...t3_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 number of symbolic links on th...

...al 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 best guess of what happened...

...ck_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.958988] EXT3-fs error (device d...