Linux ATA/IDE development
 help / color / mirror / Atom feed
From: "Leslie Rhorer" <lrhorer@satx.rr.com>
To: linux-ide@vger.kernel.org
Subject: RE: Odd RAID failure
Date: Thu, 9 Apr 2009 23:43:23 -0500	[thread overview]
Message-ID: <20090410044328.TFNN5844.cdptpa-omta02.mail.rr.com@Leslie> (raw)
In-Reply-To: <20090410022606.RHQT2520.cdptpa-omta04.mail.rr.com@Leslie>

> > 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.
> 
> I wouldn't expect it to have any diagnostic value, really.  The sync
> command
> locks up just like every other disk I/O when the event occurs.

I tried this and it doesn't seem to have made a difference.  Neither does
using noop as the scheduler.


  reply	other threads:[~2009-04-10  4:43 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
2009-04-10  2:26       ` Leslie Rhorer
2009-04-10  4:43         ` Leslie Rhorer [this message]
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=20090410044328.TFNN5844.cdptpa-omta02.mail.rr.com@Leslie \
    --to=lrhorer@satx.rr.com \
    --cc=linux-ide@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