From: Jeremy West <jkwest@gmail.com>
To: Reiserfs Mailinglist <reiserfs-list@namesys.com>
Subject: Re: reiser4 and reiserfs co-existence?
Date: Wed, 10 Nov 2004 01:04:44 -0500 [thread overview]
Message-ID: <b28a886104110922046481965d@mail.gmail.com> (raw)
In-Reply-To: <b28a886104110921518b5365b@mail.gmail.com>
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"
next prev parent reply other threads:[~2004-11-10 6:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-08 16:55 reiser4 and reiserfs co-existence? Jeremy West
2004-11-08 17:09 ` Redeeman
2004-11-09 7:16 ` Jeremy West
2004-11-09 10:41 ` mjt
2004-11-09 10:55 ` Vladimir Saveliev
2004-11-09 15:41 ` Jeremy West
2004-11-09 17:47 ` Michael Barry
2004-11-09 17:53 ` Jeremy West
2004-11-09 17:55 ` Michael Barry
2004-11-09 17:57 ` Spam
2004-11-09 18:06 ` Jeremy West
2004-11-09 18:11 ` mjt
2004-11-09 21:21 ` Jeremy West
[not found] ` <662c77ee04110913347169a645@mail.gmail.com>
2004-11-09 21:56 ` Jeremy West
2004-11-09 17:57 ` mjt
2004-11-09 18:08 ` Jeremy West
2004-11-09 19:06 ` Dr. Giovanni A. Orlando
2004-11-09 18:11 ` Jeremy West
2004-11-10 5:51 ` Jeremy West
2004-11-10 6:04 ` Jeremy West [this message]
2004-11-10 6:48 ` Jeremy West
[not found] ` <1100072902.1381.44.camel@tribesman.namesys.com>
2004-11-10 18:34 ` Jeremy West
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b28a886104110922046481965d@mail.gmail.com \
--to=jkwest@gmail.com \
--cc=reiserfs-list@namesys.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.