From: Andrej Podzimek <andrej@podzimek.org>
To: reiserfs-devel@vger.kernel.org
Subject: Problems with the 'flush-8:0' process in 2.6.35.3
Date: Sat, 28 Aug 2010 06:27:48 +0200 [thread overview]
Message-ID: <4C789044.3020403@podzimek.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1207 bytes --]
Hello,
I use a 2.6.35.3 kernel and Reiser4 as the root file system. In a couple of minutes after boot, a kernel process called 'flush-8:0' takes up all the available CPU time. From that moment on, it is impossible to sync filesystems (and suspend, hibernate or reboot). (The 'sync' command halts indefinitely.) In some cases it is even impossible to log in. Existing sessions seem to work fine, to an extent.
I first thought this was related to the GTT chipset coherency patch. (This patch fixes a one-year-old bug that caused all the Intel 855 class GPUs to be totally unusable.) However, removing the patch and testing with only a vanilla kernel (and Reiser4, of course) showed that 'flush-8:0' will eventually go mad, no matter if the GPU-related patch is present or not.
The machine is an Asus M2400N laptop with a 100GB Seagate Momentus.
Is this a known issue? How could I track this down? In fact I don't even know whether this is related to Reiser4 or not. It may be a bug in VFS. I don't use 'noflushd' or anything of that kind. (Some people reported similar problems related to noflushd. So this is not the case.) If this is unrelated to Reiser4, where should I report it?
Andrej
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 6343 bytes --]
next reply other threads:[~2010-08-28 4:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-28 4:27 Andrej Podzimek [this message]
2010-08-28 10:15 ` Problems with the 'flush-8:0' process in 2.6.35.3 Edward Shishkin
2010-08-31 0:21 ` Edward Shishkin
2010-09-15 11:41 ` Andrej Podzimek
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=4C789044.3020403@podzimek.org \
--to=andrej@podzimek.org \
--cc=reiserfs-devel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).