From: David Osojnik <david@dworf.com>
To: Mike Galbraith <efault@gmx.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: bad command responsiveness Proliant DL 585
Date: Thu, 15 Jun 2006 09:38:47 +0200 [thread overview]
Message-ID: <44910E87.3050200@dworf.com> (raw)
In-Reply-To: <1150353862.8097.61.camel@Homer.TheSimpsons.net>
Hello,
IT Works perfect when setting noatime,nodiratime on the partition!!
can i try anything else? what does this actually mean?
thanks!!
David
Mike Galbraith wrote:
>On Wed, 2006-06-14 at 21:18 +0200, David Osojnik wrote:
>
>
>>here is the output of SysRq-T and SysRq-M:
>>
>>http://www.dworf.com/sysrq.txt
>>
>>any ideas?
>>
>>
>
>Not really.
>
>I see I/O jammed up on reiserfs:.text.lock.journal, but you said
>reiserfs and ext3 both stall the same way. If the journal is in the
>raid, I'd try moving it, but I can't really imagine seek troubles
>leading to 15 minutes of grinding. I noticed that those last two
>instances of bash got nailed because of atime. Do things get any better
>if mounted noatime, nodiratime?
>
> -Mike
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at http://www.tux.org/lkml/
>
>
next prev parent reply other threads:[~2006-06-15 7:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-14 7:59 bad command responsiveness Proliant DL 585 David Osojnik
2006-06-14 9:42 ` Mike Galbraith
2006-06-14 19:18 ` David Osojnik
2006-06-15 6:44 ` Mike Galbraith
2006-06-15 7:38 ` David Osojnik [this message]
[not found] ` <44910E5B.50704@dworf.com>
2006-06-15 8:00 ` Mike Galbraith
2006-06-15 11:18 ` David Osojnik
2006-06-15 12:14 ` Mike Galbraith
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=44910E87.3050200@dworf.com \
--to=david@dworf.com \
--cc=efault@gmx.de \
--cc=linux-kernel@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