All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Greg Freemyer <greg.freemyer@gmail.com>
Cc: lrhorer@satx.rr.com, linux-ide@vger.kernel.org
Subject: Re: Odd RAID failure
Date: Thu, 09 Apr 2009 13:05:11 -0700	[thread overview]
Message-ID: <49DE54F7.1070408@kernel.org> (raw)
In-Reply-To: <87f94c370904091142m79c60d7cy2e377c40b2f7f0c1@mail.gmail.com>

Hello,

Greg Freemyer wrote:
> On Thu, Apr 9, 2009 at 2:13 PM, Tejun Heo <tj@kernel.org> wrote:
>> Lelsie Rhorer wrote:
>> ...
>>> The issue is the entire array will occasionally pause completely for about
>>> 40 seconds when a file is created.  This does not always happen, but the
>>> situation is easily reproducible.
>> Does the kernel whine about anything when this happens?
> 
> Tejun,
> 
> There is a long thread on linux-raid about this issue:
> 
> http://markmail.org/message/a32fsnsaa5mmpthw
> 
> Per the thread, Leslie is not seeing anything in the logs.

That was a long thread.  Heh... yeah, at the first look, it looks like
more of VM / FS interaction problem than low level driver problem.
Using blktrace/blkparse to track IO insertion, issue and completion
latencies would help to whether the problem is above the block layer
or below it.

If you can bear with slower operation, keeping issuing sync repeatedly
(ie. something like while true; do sync; sleep 1; done) and see how
the behavior changes might shed some light on what's going on too.
Also, disabling journal and seeing how the behavior changes could be
revealing too.

Thanks.

-- 
tejun

  reply	other threads:[~2009-04-09 20:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-04 17:32 Odd RAID failure Lelsie Rhorer
2009-04-09 18:13 ` Tejun Heo
2009-04-09 18:42   ` Greg Freemyer
2009-04-09 20:05     ` Tejun Heo [this message]
2009-04-10  2:26       ` Leslie Rhorer
2009-04-10  4:43         ` Leslie Rhorer
2009-04-10 17:01           ` Tejun Heo
2009-04-11  1:34             ` Leslie Rhorer

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=49DE54F7.1070408@kernel.org \
    --to=tj@kernel.org \
    --cc=greg.freemyer@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=lrhorer@satx.rr.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.