All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Thompson <vagabond@mapdesign.net>
To: reiserfs-list@namesys.com
Subject: Reiser4 hard locks. Volunteering for testing.
Date: Sun, 15 Aug 2004 23:07:37 +0100	[thread overview]
Message-ID: <411FDEA9.9020404@mapdesign.net> (raw)

Hi everyone, I've been trying out Reiser4 lately and I've experienced 
frequent system locks when there's lots of Disk IO activity. I'm happy 
to report debug info or whatever you guys need, you just need to let me 
know what to do and what to send you.

I'm running gentoo linux unstable, with a patched 2.6.8.1 kernel, but 
I've had similar problems on the 2.6.7 and 2.6.6 kernels over the last 
month or so (I hadn't tried reiser4 for a very long time before that). 
I've tried renicing reiser4, as mentioned in some of the threads on the 
gentoo forums, but I'm not sure what else to try.

My system is a Dual Athlon 1900++MP Asus a7m266-d with 1 gig of ram. I'm 
also using the ati kernel module, so the kernel is "tainted" I guess. i 
have a 20 gig reiser4 partition, recreated today with the latest libaal 
and reiser4progs (1.0.0). I've tried just copying files to it and it 
will just lock after an apparently random time, and the whole system 
locks, the magic sysrq key doesn't work (or after I do an emergency sync 
it fails to do anything else).

 From what I've seen of it when its not locking up its extremely fast 
and since you say Reiser4 needs more testers I'm volunteering. I'll run 
any kernel you want, turn on any debugging options whatever if it will 
help somebody track down the problem.

Thanks in advance,

Andrew

             reply	other threads:[~2004-08-15 22:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-15 22:07 Andrew Thompson [this message]
2004-08-15 22:37 ` Reiser4 hard locks. Volunteering for testing mjt

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=411FDEA9.9020404@mapdesign.net \
    --to=vagabond@mapdesign.net \
    --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.