search for: get_unused_buffer_head

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

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

...>> 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 > when you do be sure to send them /proc/slabinf...

...130979>] [<c012efa7>] [<c015de43>] [<c014b6cd>] [<c0110760>] [<c015d92b>] [<c015d800>] [<c01054e8>] Code: 8b 44 81 18 89 41 14 83 f8 ff 75 1d 8b 41 04 8b 11 89 42 04 >>EIP; c0126506 <kmem_cache_alloc+66/b0> <===== Trace; c012f292 <get_unused_buffer_head+32/80> Trace; c012f31c <create_buffers+1c/e0> Trace; c0130782 <grow_dev_page+62/a0> Trace; c0130978 <grow_buffers+b8/100> Trace; c012efa6 <getblk+26/40> Trace; c015de42 <journal_get_descriptor_buffer+32/50> Trace; c014b6cc <read_kcore+17c/480> Trace; c0110760...