search for: journal_write_metadata_buff

...006a>] [<c010b389>] [<c010b0c3>] [<c011918d>] [<c0111aa6>] [<c014c7d8>] [<c014c7f4>] [<c014c6bc>] [<c014c6a8>] [<c0108c2f>] [<c0108c38>] Code: 0f 0b 83 c4 10 89 f6 8b 4c 24 34 8b 41 18 a8 02 75 2d 83 c4 >>EIP; c014ca15 <journal_write_metadata_buffer+4d/1d8> <===== Trace; c014ce0c <journal_next_log_block+64/a0> Trace; c015006a <journal_commit_transaction+572/ed8> Trace; c010b389 <handle_IRQ_event+3d/78> Trace; c010b0c3 <do_8259A_IRQ+8f/9c> Trace; c011918d <do_bottom_half+51/6c> Trace; c0111aa6 <schedul...

...c373f600 c373f650 c373bc00 00000000 c6d98a00 00000000 c80b8000 c80b8000 Call Trace: [<c01707c7>] [<c016da27>] [<c011417d>] [<c0170220>] [<c01700d0>] [<c010560f>] Code: 0f 0b 83 c4 08 90 8d 74 26 00 8b 7c 24 2c 8b 47 0c 85 c0 74 >>EIP; c0170396 <journal_write_metadata_buffer+6a/2cc> <===== Trace; c01707c7 <journal_next_log_block+7b/80> Trace; c016da27 <journal_commit_transaction+7a3/1155> Trace; c011417d <schedule+585/648> Trace; c0170220 <kjournald+140/1d8> Trace; c01700d0 <commit_timeout+0/c> Trace; c010560f <kernel_thread+2...

Red Hat 2.2.19-6.2.12 + 0.0.7a + https://listman.redhat.com/pipermail/ext3-users/2001-November/002258.html (not tuned in /proc yet) + journal 4MB on each fs + 6 ext3 fs on raid1 (hda+hdc) + 1 ext3 fs on another disk not on raid1 (hdd) While untarring (tar zxf) a file that was on a ext3/raid1 onto hdd I got: ksymoops 2.3.4 on i686 2.2.19-6.2.12.g1. Options used -V (default) -k

...g. kernel is 2.2.19pre7 (with openwall patches, although it should not matter), ext3 is 0.05e. All filesystems are ext3 (in journal data mode). Machine is PIII/600 with 128MB RAM, 300MB swap. Journals are 5-15MB in size. Partitions are 150MB to 7,5GB. Feb 5 12:28:28 blue kernel: Buffer locked in journal_write_metadata_buffer, flags 0x00004a0f, count 1 Feb 5 12:28:28 blue kernel: kernel BUG at journal.c:306! Feb 5 12:28:28 blue kernel: invalid operand: 0000 Feb 5 12:28:28 blue kernel: CPU: 0 Feb 5 12:28:28 blue kernel: EIP: 0010:[journal_write_metadata_buffer+71/440] Feb 5 12:28:28 blue kernel: EFLAGS:...

Hello All, I am running Linux 2.4.7-10, 2.4.18-4 and 2.4.19-pre9, I see the following oops quite often (mainly on 2.4.19-pre9 with kdb). All the kernels I use have the kdb patch installed. 1 kmem_cache_alloc (offset 0x125) get_unused_buffer_head journal_write_metadata_buffer journal_commit_transaction kjournald kernel_thread kmem_cache_alloc dis xchg %eax, (%ebx) cmp $0x5a2cf071, %eax (where did a value like that come from?) je .... ud2a - (looks like assembly for BUG()) One more thing I have seen is a problem with the following code do {...

...ocal to simplify troubleshooting... same problem with an NFS source) rsync command used: rsync -Wav --stats /sourcedir /destdir >> /opt/rsync.log 2>&1 and syslog reports: Aug 31 04:07:57 moss kernel: ENOMEM in do_get_write_access, retrying. Aug 31 04:16:05 moss kernel: journal_write_metadata_buffer: ENOMEM at get_unused_buffer_head, trying again. anyone seen this? -- Matt Miller IT Infrastructure Team Duke University - Fuqua School of Business

Back again with another oops, which looks suspiciously similiar to the one i posted some days ago (https://listman.redhat.com/pipermail/ext3-users/2002-May/003587.html). Jun 11 12:11:30 castor kernel: Assertion failure in journal_write_metadata_buffer() at journal.c:406: "buffer_jdirty(jh2bh(jh_in))" ksymoops 0.7c on i686 2.4.18-4custom. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.4.18-4custom/ (default) -m /boot/System.map-2.4.18-4 (specified) Warning (c...

...>> >> >> rsync command used: >> rsync -Wav --stats /sourcedir /destdir >> /opt/rsync.log 2>&1 >> >> and syslog reports: >> Aug 31 04:07:57 moss kernel: ENOMEM in do_get_write_access, retrying. >> Aug 31 04:16:05 moss kernel: journal_write_metadata_buffer: ENOMEM >> at get_unused_buffer_head, trying again. >> >> anyone seen this? > > Not an rsync problem. This is a kernel issue. > > You seem to be out of ZONE_DMA memory. I don't know whether > you should be reporting this to RH or Veritas or IBM but >...

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

...b_state:0xb1 b_list:BUF_CLEAN b_jlist:BJ_Metadata on_lru:1 cpu:0 on_hash:1 b_count:3 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:0 b_trans_is_comitting:1 b_jcount:0 <0> journal_write_metadata_buffer() [journal.c:466] file as BJ_Shadow b_state:0xb1 b_list:BUF_CLEAN b_jlist:BJ_Metadata on_lru:1 cpu:0 on_hash:1 b_count:3 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:0 b_tra...

The following 6 patches cleanup the jbd code and kill about 200 lines. First of 4 patches can apply to 2.6.13-git8 and 2.6.13-mm2. The rest of them can apply to 2.6.13-mm2. fs/jbd/checkpoint.c | 179 +++++++++++-------------------------------- fs/jbd/commit.c | 101 ++++++++++-------------- fs/jbd/journal.c | 11 +- fs/jbd/revoke.c | 158