From: Damien Wyart <damien.wyart@free.fr>
To: reiserfs-list@namesys.com
Subject: ent:sdXnn going to D state with latest reiser4 patch
Date: Sun, 18 Sep 2005 22:29:04 +0200 [thread overview]
Message-ID: <20050918202904.GA3025@localhost.localdomain> (raw)
Hello,
Doing some tests with latest reiser4 patches from 2.6.14-mm1, I noticed
that the load of the machine never goes under 2. It comes from two
processes related to reiser4 and going to D state immediately after the
filesystems are mounted. As there are two reiser4 partitions, I get two
such processes, and the load is always higher than 2. These processes
appear as ent:sdb7 and ent:sdb11 (correspnding fs are on sdb7 and sdb11)
and same with square brackets sometimes.
I can reproduce this with 2.6.14-rc1-git4 and 2.6.13.2, with the latest
patch. I do not have this problem with previous reiser4 patch
(2.6.13-mm3 + latest reiser4-only.1.patch from ftp.namesys.com.
I guess people doing simple tests of this patch will see this behaviour,
and I am surprised nobody seems to have posted about this on the list.
Best regards,
--
Damien Wyart
next reply other threads:[~2005-09-18 20:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-18 20:29 Damien Wyart [this message]
2005-09-18 21:31 ` ent:sdXnn going to D state with latest reiser4 patch Laurent Riffard
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=20050918202904.GA3025@localhost.localdomain \
--to=damien.wyart@free.fr \
--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.