Basically any heavy activity on the partition seems to trigger it. Here's a short transcript:
dually ~ # cat /proc/version
Linux version 2.6.16-rc2-mm1 ([EMAIL PROTECTED]) (gcc version 3.3.6 (Gentoo 3.3.6, ssp-3.3.6-1.0, pie-8.7.8)) #7 SMP PREEMPT Thu Feb 16 21:19:53 Local time zone must be set--
dually ~ # mkfs.reiser4 --version
mkfs.reiser4 1.0.5
Copyright (C) 2001, 2002, 2003, 2004 by Hans Reiser, licensing governed by
reiser4progs/COPYING.
dually ~ # mkfs.reiser4 /dev/sdb1 --yes
dually ~ # mount /dev/sdb1 /data1
dually ~ # klogd -d -f ~/kernel.log
dually ~ # cd /data1
dually data1 # cp -ra /usr/src/linux-2.6.16-rc2-mm1/ .
dually data1 # tar cf linux.bz2 linux-2.6.16-rc2-mm1/
...after about half a minute of activity I receive the message which I've attached as a small JPEG
"reiser4 panicked cowardly: reiser4[tar(4078)] commit_current_atom (fs/reiser4/txnmgr.c:1130) [zam-597]:". I can't see whether it was line 1130 or 1138. I'll take a quick look myself, but I'm completely unfamiliar with reiser4 sources and the kernel sources in general.
After this my system is completely locked up. When I mount the partition after restarting it no longer contains any files. I have few or no problems when creating, mounting, and working on reiser4 partitions when booted from the System recovery liveCD so it must be something in the latest sources or in my kernel configuration(which is 100% stable for everything else under reiser3, but I haven't bothered to perfect yet).
Apologies about the JPEG, I could not figure out how to get the kernel output logged into a file(maybe it freezes before the file can flush to disk, i dunno). If you know of a way, I welcome instruction.
On 2/21/06, Vladimir V. Saveliev <[EMAIL PROTECTED]> wrote:
Hello
On Fri, 2006-02-17 at 10:43 -0600, John Cohorn wrote:
> Is there a known issue with 2.6.16-xxx-mm1? I too am having severe and
> very random, but reproducible problems which will completely lock up
> my machine minutes after mounting an R4 partition if not seconds. I
> did try disabling 4K stacks in my .config. Also, this is an Athlon 64
> X2 I'm running with so maybe there are SMP issues?
no, it does not look so.
> One of my friends said that Reiser4 became unstable for him also when
> he upgraded to a dual core Athlon64...but until I test for myself
> that's just a wild theory that it's an SMP bug. This machine is
> otherwise stable in Memtest, in Windows playing the latest games, and
> on Linux compiling huge amounts of software.
>
> If there are not known issues with the latest kernels then I will
> happily try to send detailed configurations and logs of what's
> happening this evening. I have two shiny new 250GB SATA drives on my
> machine and I can test freely with one of them until I need the space.
> I'd love to help squash any bugs that I can :)
>
If you described the exact sequence of commands which makes reiser4 to
crash - that would help a lot.
