Re: reiser4 and reiserfs co-existence?

[Jeremy West <jkwest@gmail.com>]

Before I head off to bed, I was able to obtain a better log of a
segfault.  After rebooting from the problem I had with zombie threads,
I tried restarting my kernel compilation.  It died right away.  Here
is the end of the kernel file

bash-2.05b# ls
current  log-2004-11-08-08:16:05  log-2004-11-09-08:32:37
bash-2.05b# tail -f current 
Nov 10 01:32:53 [kernel] NVRM: loading NVIDIA Linux x86 NVIDIA Kernel
Module  1.0-6629  Wed Nov  3 13:12:51 PST 2004
Nov 10 01:32:57 [kernel] process `named' is using obsolete setsockopt
SO_BSDCOMPAT
Nov 10 01:33:16 [kernel] NVRM: not using NVAGP, AGPGART is loaded!!
                - Last output repeated twice -
Nov 10 01:36:27 [kernel] loop: loaded (max 8 devices)
Nov 10 01:36:27 [kernel] EXT2-fs warning: mounting unchecked fs,
running e2fsck is recommended
Nov 10 01:43:27 [kernel] reiser4[fixdep(7878)]: find_file_state
(fs/reiser4/plugin/file/file.c:487)[vs-1074]:
Nov 10 01:43:27 [kernel] code: -2 at fs/reiser4/search.c:1278
Nov 10 01:43:27 [kernel] context: trace_flags: 0
Nov 10 01:43:27 [kernel] ------------[ cut here ]------------


--Jeremy


On Wed, 10 Nov 2004 01:04:44 -0500, Jeremy West <jkwest@gmail.com> wrote:
> Here is an error for you all.  From my /var/log/everything log.
> 
> -----------------------
> Nov 10 00:30:01 [/usr/sbin/cron] (root) CMD (test -x /usr/sbin/run-crons && /usr
> /sbin/run-crons )
>                 - Last output repeated 2 times -
> Nov 10 00:50:58 [kernel] reiser4[g++(10858)]: check_dkeys (fs/reiser4/search.c:1
> 084)[vs-1199]
> -----------------------
> 
> This happened while I was compiling a kernel, compiling kdeedu, and I
> was listening to music through alsa.  While I was listening to music,
> I restarted alsa.  The compiles both died, and one of them created a
> zombie process.
> 
> Here is the output in one console as it was compiling kdeedu.  After I
> noticed the build processes had stopped (by using "top" command), I
> tried "ctrl-c" to kill the kdeedu compile.  Here is the last bit.
> This runaway build spawned the "zombie" proces.
> 
> ---------------------
> g++ -DHAVE_CONFIG_H -I. -I. -I../.. -I../.. -I/usr/kde/3.3/include
> -I/usr/qt/3/include -I/usr/X11R6/include   -DQT_THREAD_SUPPORT
> -D_REENTRANT  -Wnon-virtual-dtor -Wno-long-long -Wundef -ansi
> -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wconversion
> -Wchar-subscripts -Wall -W -Wpointer-arith -Wwrite-strings -DNDEBUG
> -DNO_DEBUG -O2 -O2 -march=athlon-xp -fomit-frame-pointer
> -Wformat-security -Wmissing-format-attribute -fno-exceptions
> -fno-check-new -fno-common -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST
> -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -D_GNU_SOURCE -c -o
> ksfilereader.o ksfilereader.cpp
> Caught signal 2 in pid 20302
> Pid 20302 alreadly caught signal and is still cleaning up
> Pid 20302 alreadly caught signal and is still cleaning up
> -------------------------------
> #uname -a
> Linux homer1 2.6.9+reiser4 #1 Tue Nov 9 02:30:12 EST 2004 i686 AMD
> 
> 
> Athlon(tm) XP 2600+ AuthenticAMD GNU/Linux
> 
> Jeremy West
> //---------------------------
> "I had a life once... now I have a computer and DSL"
> 


-- 
Jeremy West
//---------------------------
"I had a life once... now I have a computer and DSL"