From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Matthias Schniedermeyer <ms@citd.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel 2.6.6 & 2.6.7 sometime hang after much I/O
Date: Sun, 20 Jun 2004 20:29:20 +1000 [thread overview]
Message-ID: <40D56700.2030206@yahoo.com.au> (raw)
In-Reply-To: <Pine.LNX.4.44.0406201123240.26522-100000@korben.citd.de>
Matthias Schniedermeyer wrote:
> Hi
>
>
>
> First. Kernels <= 2.6.5 don't have this problem. After 2.6.6 show this
> behaviour sometimes i downgraded to 2.6.5 as i thought that it would be
> fixed in 2.6.7, but 2.6.7 also show this behaviour.
>
> The I/O i do is split some large files (>2GB) into smaller files <= 2GB.
> Sometimes the process that does this just hangs (currently i have such a
> hangung process), top currently shows up to 90% I/O-Wait.
>
> SOME of my "konsole"s(xterm) hang then too, but others don't (like this
> where i type this email) starting new "konsole"s sometimes work, sometimes
> not.
>
> System is:
> Distribution: Debian SID.
> 2xP3-933Mhz, 3GB-RAM, Serverworks HE-SL-Chipset
> "System"-HDD is SCSI connected via Symbios-53c1010 (Dual U160)
> "Data"-HDD(s)(where the split-process does it's work) is connected to a
> Highpoint RocketRAID 1540 (HPT-374 Chipset)
> Filesystem is XFS for the Data-HDD(s) and Reiserfs for the system-HDD.
>
> If other info is needed i will provide them.
>
When the process has hung, press Alt + SysRq + T to get a task
trace. Run
dmesg -s 1000000 > tmp
and send us tmp. You'd better send your .config and dmesg too.
Thanks
next prev parent reply other threads:[~2004-06-20 10:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-20 9:41 Kernel 2.6.6 & 2.6.7 sometime hang after much I/O Matthias Schniedermeyer
2004-06-20 10:29 ` Nick Piggin [this message]
2004-06-20 11:59 ` Matthias Schniedermeyer
2004-06-20 13:05 ` Nick Piggin
2004-06-20 14:17 ` Matthias Schniedermeyer
2004-06-20 14:19 ` Jens Axboe
2004-06-20 14:43 ` Matthias Schniedermeyer
2004-06-20 14:38 ` Matthias Schniedermeyer
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=40D56700.2030206@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=ms@citd.de \
/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.