I tried 2.6.17-mm6 (was the latest at the time) and reiser4 still always
fails when it runs out of memory. My test has been building a kernel
with enough jobs to exhaust memory. Expecting problems, I began by
testing reiser4 with debugging enabled.
The first time, I got the panic below after running "while true ; do
make mrproper && zcat /proc/config.gz > .config && make -j64 ; done" in
linux-2.6.17-mm6 (on a fresh test filesystem) for an unknown duration of
time.
reiser4 panicked cowardly: reiser4[cc1(12238)]: page_bio
(fs/reiser4/page_cache.c:434)[nikita-2276]:
Kernel panic - not syncing: reiser4[cc1(12238)]: page_bio
(fs/reiser4/page_cache.c:434)[nikita-2276]:
The next two times, after about half an hour of the above command I got
the panic below (except the second time was with cc1 instead of fixdep).
reiser4 panicked cowardly: reiser4[fixdep(19463)]: sibling_list_remove
(fs/reiser4/tree_walk.c:813)[zam-32245]:
Kernel panic - not syncing: reiser4[fixdep(19463)]: sibling_list_remove
(fs/reiser4/tree_walk.c:813)[zam-32245]:
The third time the filesystem wasn't clean after a reboot. fsck.reiser4
--check logged:
http://people.msoe.edu/~maciejej/patches/AMD64_reiser4_debug/20060711/fsck3_--check.txt.gz
fsck.reiser4 --fix logged:
http://people.msoe.edu/~maciejej/patches/AMD64_reiser4_debug/20060711/fsck3_--fix.txt.gz
Another --check turned up clean:
http://people.msoe.edu/~maciejej/patches/AMD64_reiser4_debug/20060711/fsck3_--check_after_--fix.txt.gz
Things got slightly more interesting with debugging disabled. The first
time I got the following OOPS after some "flushing like mad" messages. A
bunch of cc1 process were stuck in the D state.
http://people.msoe.edu/~maciejej/patches/AMD64_reiser4_debug/20060711/messages4.txt.gz
http://people.msoe.edu/~maciejej/patches/AMD64_reiser4_debug/20060711/fsck4_--check.txt.gz
http://people.msoe.edu/~maciejej/patches/AMD64_reiser4_debug/20060711/fsck4_--fix.txt.gz
http://people.msoe.edu/~maciejej/patches/AMD64_reiser4_debug/20060711/fsck4_--check_after_--fix.txt.gz
The second time I got:
http://people.msoe.edu/~maciejej/patches/AMD64_reiser4_debug/20060711/messages5.txt.gz
http://people.msoe.edu/~maciejej/patches/AMD64_reiser4_debug/20060711/fsck5_--check.txt.gz
http://people.msoe.edu/~maciejej/patches/AMD64_reiser4_debug/20060711/fsck5_--fix.txt.gz
http://people.msoe.edu/~maciejej/patches/AMD64_reiser4_debug/20060711/fsck5_--check_after_--fix.txt.gz
On Fri, 2006-07-07 at 17:16 +0400, Vladimir V. Saveliev wrote:
> Hello
>
> On Fri, 2006-07-07 at 01:18 -0600, Jake Maciejewski wrote:
> > It doesn't look like this issue has been fixed:
> >
> > http://people.msoe.edu/~maciejej/patches/AMD64_reiser4_debug/20060702/reiser4_kio_http.txt.gz
> >
> > Again fsck showed a clean filesystem. Should I try -mm?
> >
>
> Yes, please try to check whether latest mm has this problem.
>
> > This is somewhat difficult to reproduce because the critical factor
> > seems to be using all available memory, however in doing so the system
> > quickly becomes unresponsive.
> >
> > On Mon, 2006-07-03 at 17:23 -0600, Jake Maciejewski wrote:
> > > Thanks for the patch. I don't think I'll be able to test it before
> > > Wednesday, though.
> > >
> > > On Mon, 2006-07-03 at 14:10 +0400, Vladimir V. Saveliev wrote:
> > > > Hello
> > > >
> > > > On Sun, 2006-07-02 at 22:24 -0600, Jake Maciejewski wrote:
> > > > > I'm seeing this on 2.6.16.20 with the -4 patch, amd64 with preempt.
> > > > > The
> > > > > OOM killer was called even though I have 1GB RAM and 4GB swap. My logs
> > > > > are available at:
> > > > >
> > > > > http://people.msoe.edu/~maciejej/patches/AMD64_reiser4_debug/20060702/oom.txt.gz
> > > > >
> > > > > Both affected filesystems (rsync was using one filesystem, cc1 the
> > > > > other) came up clean with fsck.
> > > > >
> > > > > On Sat, 2006-07-01 at 22:08 +0200, Łukasz Mierzwa wrote:
> > > > > > I'm running x86 gentoo system with / on reiser4, I'm using
> > > > > > suspend-sources-2.6.16-r8 kernel with 2.6.16-4 patch. Today I run
> > > > > > emerge
> > > > > > --sync, after that I started to compile new xine-lib while browsing
> > > > > > net,
> > > > > > when xine-lib was finishing I got this errors:
> > > > > >
> > > > > > kernel BUG at fs/inode.c:253!
> > > >
> > > > would you please check whether this patch helps?
> > > > ftp://ftp.ru.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.17/2.6.17-mm5/broken-out/reiser4-run-truncate_inode_pages-in-reiser4_delete_inode.patch
> > > >
> > > >
> > > > > > invalid opcode: 0000 [#1]
> > > > > > PREEMPT
> > > > > > Modules linked in: ndiswrapper fglrx acer_acpi nsc_ircc irda
> > > > > > crc_ccitt
> > > > > > snd_atiixp snd_ac97_codec snd_ac97_bus yenta_socket rsrc_nonstatic
> > > > > > pcmcia_core tifm_7xx1 tifm_core
> > > > > > CPU: 0
> > > > > > EIP: 0060:[<c017bc56>] Tainted: P VLI
> > > > > > EFLAGS: 00010206 (2.6.16-suspend2-r8 #2)
> > > > > > EIP is at clear_inode+0x16/0xb0
> > > > > > eax: 00000003 ebx: d5245d20 ecx: 00000000 edx: d5245df8
> > > > > > esi: df2099c0 edi: c2a3a000 ebp: c2a3a000 esp: c2a3be94
> > > > > > ds: 007b es: 007b ss: 0068
> > > > > > Process emerge (pid: 9123, threadinfo=c2a3a000 task=c2a0ba70)
> > > > > > Stack: <0>df2099c0 d5245d20 df2099c0 c01db519 c017a385 00000000
> > > > > > 00000400
> > > > > > d5245e28
> > > > > > d5245d20 c2a3a000 d415c114 d5245d20 c01db4e0 c017bd59
> > > > > > d5245d20
> > > > > > dfe9b000
> > > > > > c017b81c d415c114 c017a431 00000000 dfe9b000
> > > > > > df533000
> > > > > > c2a3bf50 c0172d74
> > > > > > Call Trace:
> > > > > > [<c01db519>] reiser4_delete_inode+0x39/0xc0
> > > > > > [<c017a385>] dput+0x25/0x170
> > > > > > [<c01db4e0>] reiser4_delete_inode+0x0/0xc0
> > > > > > [<c017bd59>] generic_delete_inode+0x69/0x100
> > > > > > [<c017b81c>] iput+0x5c/0x70
> > > > > > [<c017a431>] dput+0xd1/0x170
> > > > > > [<c0172d74>] sys_renameat+0x1c4/0x1f0
> > > > > > [<c0172dc7>] sys_rename+0x27/0x30
> > > > > > [<c0102ef3>] sysenter_past_esp+0x54/0x75
> > > > > > Code: 80 98 00 00 00 8b 40 38 eb c4 8d 74
> > > > > > 26 00 8d
> > > > > > bc 27 00 00 00 00 56 53 89 c3 83 ec 04 e8 14 b0 fe ff 8b 83 c4 00
> > > > > > 00 00 85
> > > > > > c0 74 08 <0f> 0b fd 00 ab d4 37 c0 8b 83 20 01 00 00 a8 10 75 08 0f
> > > > > > 0b ff
> > > > > > <4>reiser4[emerge(9123)]:
> > > > > > release_unix_file
> > > > > > (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> > > > > > WARNING: out of memory?
> > > > > > reiser4[emerge(9123)]: release_unix_file
> > > > > > (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> > > > > > WARNING: out of memory?
> > > > > > reiser4[emerge(9123)]: release_unix_file
> > > > > > (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> > > > > > WARNING: out of memory?
> > > > > > reiser4[emerge(9123)]: release_unix_file
> > > > > > (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> > > > > > WARNING: out of memory?
> > > > > > reiser4[emerge(9123)]: release_unix_file
> > > > > > (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> > > > > > WARNING: out of memory?
> > > > > > reiser4[emerge(9123)]: release_unix_file
> > > > > > (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> > > > > > WARNING: out of memory?
> > > > > > reiser4[emerge(9123)]: release_unix_file
> > > > > > (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> > > > > > WARNING: out of memory?
> > > > > > reiser4[emerge(9123)]: release_unix_file
> > > > > > (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> > > > > > WARNING: out of memory?
> > > > > > reiser4[emerge(9123)]: release_unix_file
> > > > > > (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> > > > > > WARNING: out of memory?
> > > > > > reiser4[emerge(9123)]: release_unix_file
> > > > > > (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> > > > > > WARNING: out of memory?
> > > > > > reiser4[emerge(9123)]: release_unix_file
> > > > > > (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> > > > > > WARNING: out of memory?
> > > > > > reiser4[emerge(9123)]: release_unix_file
> > > > > > (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> > > > > > WARNING: out of memory?
> > > > > > reiser4[emerge(9123)]: release_unix_file
> > > > > > (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> > > > > > WARNING: out of memory?
> > > > > > reiser4[emerge(9123)]: release_unix_file
> > > > > > (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> > > > > > WARNING: out of memory?
> > > > > > reiser4[emerge(9123)]: release_unix_file
> > > > > > (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> > > > > > WARNING: out of memory?
> > > > > > reiser4[emerge(9123)]: release_unix_file
> > > > > > (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> > > > > > WARNING: out of memory?
> > > > > > reiser4[emerge(9123)]: release_unix_file
> > > > > > (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> > > > > > WARNING: out of memory?
> > > > > > reiser4[emerge(9123)]: release_unix_file
> > > > > > (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> > > > > > WARNING: out of memory?
> > > > > > reiser4[emerge(9123)]: release_unix_file
> > > > > > (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> > > > > > WARNING: out of memory?
> > > > > > reiser4[emerge(9123)]: release_unix_file
> > > > > > (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> > > > > > WARNING: out of memory?
> > > > > > reiser4[emerge(9123)]: release_unix_file
> > > > > > (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> > > > > > WARNING: out of memory?
> > > > > > reiser4[emerge(9123)]: release_unix_file
> > > > > > (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> > > > > > WARNING: out of memory?
> > > > > > reiser4[emerge(9123)]: release_unix_file
> > > > > > (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> > > > > > WARNING: out of memory?
> > > > > > reiser4[emerge(9123)]: release_unix_file
> > > > > > (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> > > > > > WARNING: out of memory?
> > > > > > reiser4[emerge(9123)]: release_unix_file
> > > > > > (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> > > > > > WARNING: out of memory?
> > > > > > reiser4[emerge(9123)]: release_unix_file
> > > > > > (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> > > > > > WARNING: out of memory?
> > > > > > reiser4[emerge(9123)]: release_unix_file
> > > > > > (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> > > > > > WARNING: out of memory?
> > > > > > reiser4[emerge(9123)]: release_unix_file
> > > > > > (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> > > > > > WARNING: out of memory?
> > > > > > reiser4[emerge(9123)]: release_unix_file
> > > > > > (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> > > > > > WARNING: out of memory?
> > > > > > reiser4[emerge(9123)]: release_unix_file
> > > > > > (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> > > > > > WARNING: out of memory?
> > > > > > reiser4[emerge(9123)]: release_unix_file
> > > > > > (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> > > > > > WARNING: out of memory?
> > > > > > reiser4[emerge(9123)]: release_unix_file
> > > > > > (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> > > > > > WARNING: out of memory?
> > > > > > reiser4[emerge(9123)]: release_unix_file
> > > > > > (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> > > > > > WARNING: out of memory?
> > > > > > reiser4[emerge(9123)]: release_unix_file
> > > > > > (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> > > > > > WARNING: out of memory?
> > > > > > reiser4[emerge(9123)]: release_unix_file
> > > > > > (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> > > > > > WARNING: out of memory?
> > > > > > reiser4[emerge(9123)]: release_unix_file
> > > > > > (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> > > > > > WARNING: out of memory?
> > > > > > reiser4[emerge(9123)]: release_unix_file
> > > > > > (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> > > > > > WARNING: out of memory?
> > > > > > reiser4[emerge(9123)]: release_unix_file
> > > > > > (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> > > > > > WARNING: out of memory?
> > > > > > reiser4[emerge(9123)]: release_unix_file
> > > > > > (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> > > > > > WARNING: out of memory?
> > > > > > reiser4[emerge(9123)]: release_unix_file
> > > > > > (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> > > > > > WARNING: out of memory?
> > > > > > reiser4[emerge(9123)]: release_unix_file
> > > > > > (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> > > > > > WARNING: out of memory?
> > > > > >
> > > > > > I rebooted, remounted / read only and run fsck --fix, I had to run
> > > > > > fsck
> > > > > > --build-fs becouse of fatal corruptions, I got whole lot of errors
> > > > > > referring to /usr/portage dir but fs is now ok.
> > > >
>
--
Jake Maciejewski <[EMAIL PROTECTED]>
