search for: journal_bmap

...channel 0 id 5 lun 0 Nov 21 04:05:11 attila kernel: SCSI disk error : host 0 channel 0 id 5 lun 0 return code = 50000 Nov 21 04:05:11 attila kernel: I/O error: dev 08:01, sector 0 Nov 21 04:05:14 attila kernel: I/O error: dev 08:01, sector 12472 Nov 21 04:05:14 attila kernel: Assertion failure in journal_bmap() at journal.c:636: "ret != 0" Nov 21 04:05:14 attila kernel: invalid operand: 0000 Nov 21 04:05:14 attila kernel: CPU: 0 Nov 21 04:05:18 attila kernel: EIP: 0010:[journal_bmap+70/96] Not tainted Nov 21 04:05:18 attila kernel: EIP: 0010:[<c0167996>] Not tainted Nov 21...

Getting this oops on one of our production servers pretty much hangs the server. Do we have a corrupted Journal? how would ewe rebuild it? Any idea how to recover from it? Assertion failure in journal_bmap() at journal.c:636: "ret != 0" invalid operand: 0000 CPU: 0 EIP: 0010:[journal_bmap+70/96] Not tainted EIP: 0010:[<c016b646>] Not tainted EFLAGS: 00010282 eax: 00000044 ebx: 00000000 ecx: 00000002 edx: f7121f64 esi: d93e88e0 edi: f122f700 ebp: f7b58e00 esp...

Hi everyone, So this question is more for people who are familiar with the internals of ext3. I notice that the function journal_init_dev() sets the value journal->j_blk_offset = start This means that start can be any arbitrary block number on the device. However, later in the function journal_bmap() it is never actually used. The value of *retp in journal_bmap() is set to *retp = blocknr; /* + journal->j_blk_offset */ A comment on the top of journal_bmap() says that the addition can be included in the above operation if so be the need. Is there any specific reason (related to perform...

Hello, I've got a problem that is not solved after an e2fsck. What happens is that the kernel (vanilla 2.6.12) does this: journal_bmap: journal block not found at offset 1036 on hda6 Aborting journal on device hda6. ext3_abort called. The filesystem is mounted with errors=panic, so the system reboots. At boot-up an e2fsck is run on /dev/hda6. Sometimes it finds errors, sometimes not. Example: e2fsck 1.35 (28-Feb-2004) data: re...

...It goes like this: #!/bin/bash i=1000 for((i=0;i != 301;i++)); do time -p dd if=/dev/zero of=./bigfile.$i bs=1024k count=1024 echo $i done About 4 files in, it dies with 'dd: writing `./bigfile.4': Read-only file system' In the messages file, I see: Mar 27 17:28:15 r5 kernel: journal_bmap: journal block not found at offset 1607 on sd(8,17) Mar 27 17:28:15 r5 kernel: Aborting journal on device sd(8,17). Mar 27 17:28:15 r5 kernel: ext3_abort called. Mar 27 17:28:15 r5 kernel: EXT3-fs abort (device sd(8,17)): ext3_journal_start: Detected aborted journal Mar 27 17:28:15 r5 kernel: Rem...

Right now I'm building a 2.4.17 kernel on an HPPA Linux system. The kernel it ships with supports ext2 only. Has anybody tried ext3 on HPPA? -- Ralf Hildebrandt (Im Auftrag des Referat V A) Ralf.Hildebrandt@charite.de Charite Campus Virchow-Klinikum Tel. +49 (0)30-450 570-155 Referat V A - Kommunikationsnetze - Fax. +49 (0)30-450 570-916 "A man who

I remember that there used to be a problem with disk quotas on Ext3 and Raid5 on the 2.4.x kernel series. I am running 2.4.14 with Ext3 and Raid5 and am having problems with quotas and am wondering if I have something misconfigured or if this combination doesn't work yet. -- Daniel R. Bidwell | bidwell@andrews.edu Andrews University Information Technology Services If two always agree, one of

...bort_hard (journal_t *); -extern void __journal_abort_soft (journal_t *, int); extern void journal_abort (journal_t *, int); extern int journal_errno (journal_t *); -extern void journal_ack_err (journal_t *); extern int journal_clear_err (journal_t *); extern int journal_bmap(journal_t *, unsigned long, unsigned long *); extern int journal_force_commit(journal_t *); --- linux-2.6.12-rc2-mm3-full/fs/jbd/journal.c.old 2005-04-21 03:39:53.000000000 +0200 +++ linux-2.6.12-rc2-mm3-full/fs/jbd/journal.c 2005-04-21 03:45:07.000000000 +0200 @@ -59,17 +59,14 @@ EXPORT_SYMBO...