All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Artur Makówka" <juice@ursynow.2a.pl>
To: reiserfs-list@namesys.com
Subject: reiser4, crashing
Date: Sun, 01 Jan 2006 18:32:52 +0100	[thread overview]
Message-ID: <43B81244.6080503@ursynow.2a.pl> (raw)

Hello, i've been experiencing crashes for more than 2 months, and i'm 
trying to figure out what is causing it. I sent to this list few 
description of my problem, but you said it is not fault of reiser4.

I still have to hard proofs, but my apt-get is still very slow, and vim 
is also not very fast (even when my reiser4 partition is mounted with 
noatime and nodiratime)

last thing im noticing just before crash is this process:

965 root      10  -5     0    0    0 D  0.8  0.0   0:02.35 ent:hda2!

when everything works fine, its also in memory but like this:

root       965  0.0  0.0      0     0 ?        S<   17:41   0:00 [ent:hda2.]

maybe its normal, but after i tried to get help on many forums, and from 
many people, nobody really knows whats going on on my server.

its kernel 2.6.14.3 with latest reiser4 patch for this kernel, and i 
have these problems for more than 2 months, i've been stracing/gdbimg 
all process on my server, especially apache as it is taking the most 
resources, but i cant figure out anything strange.

besides IOWait is huge, like 30% on procinfo.

i heard in some situations it is possible for reiser4 developer to log 
in on server and see everything. Since i've been trying to debug it for 
so long, is it possible to do it in this situation?

There is nothing in any logs, so i can't do anything, i could turn on 
reiser4.debug but my machine is busy and i dont know how this will 
affect the performance



             reply	other threads:[~2006-01-01 17:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-01 17:32 Artur Makówka [this message]
2006-01-03 18:24 ` reiser4, crashing Hans Reiser

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=43B81244.6080503@ursynow.2a.pl \
    --to=juice@ursynow.2a.pl \
    --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.