From: Hans Reiser <reiser@namesys.com>
To: rvalles <rvalles@es.gnu.org>
Cc: reiserfs-list@namesys.com, vitaly@thebsh.namesys.com
Subject: Re: Trouble with 2.6.13.4-reiser4-4
Date: Mon, 31 Oct 2005 22:46:54 -0800 [thread overview]
Message-ID: <43670F5E.9030108@namesys.com> (raw)
In-Reply-To: <20051101015551.GA1059@148.Red-217-126-33.pooles.rima-tde.net.>
rvalles wrote:
>I've been using reiser4 for a while (since last december). Recently,
>I've upgraded from 2.6.12 to 2.6.13.4 patched with the reiser4 -4 patch
>available on the namesys ftp.
>For some reason, since using this kernel, every now and then the
>filesystem hits the disk really hard for 15 seconds or so blocking IO
>for a program or two (I guess those that triggered the problem) and
>slowing down IO seriously for others. It may be triggered by something
>as easy as pasting some text from firefox to a xterm running vim, and
>the text won't get pasted until the HD hitting ends.
>Just in case, I've booted a recent knoppix and ran the most recent fsck
>(thank you unionfs and apt-get) on the partition. It fixed some little
>stuff extents-related that didn't look serious at all. It didn't fix
>this, tho.
>Maybe it's worth noting that there are no reiser4 related errors or
>warnings, nor IO related, on syslog.
>I can provide more debug-related information on request. I'm looking
>forward for a patch against plain 2.6.14 (not -mm, that breaks stuff I
>need and is by itself far too unstable for my taste) to see if it fixes
>anything, too.
>Cheers.
>
>
We have a patch coming out any day now that will be a lot more stable
than what is currently the latest.
Vitaly, please label our latest as not very stable in the meantime.
hans
next parent reply other threads:[~2005-11-01 6:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20051101015551.GA1059@148.Red-217-126-33.pooles.rima-tde.net.>
2005-11-01 6:46 ` Hans Reiser [this message]
2005-11-02 14:58 ` Trouble with 2.6.13.4-reiser4-4 Artur Makowka
2005-11-01 1:55 rvalles
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=43670F5E.9030108@namesys.com \
--to=reiser@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=rvalles@es.gnu.org \
--cc=vitaly@thebsh.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.