All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Friesen <chris.friesen@genband.com>
To: Neil Brown <neilb@suse.de>,
	linux-raid@vger.kernel.org, Jens Axboe <axboe@kernel.dk>
Subject: getting I/O errors in super_written()...any ideas what would cause this?
Date: Wed, 28 Nov 2012 11:52:17 -0600	[thread overview]
Message-ID: <50B64F51.6000402@genband.com> (raw)


Hi,

I'm running 2.6.27 with LVM over software RAID 1 over a pair of SAS disks.

Recently we started seeing messages of the following pattern:

Nov 28 08:57:10 kernel: end_request: I/O error, dev sda, sector 1758169523
Nov 28 08:57:10 kernel: md: super_written gets error=-5, uptodate=0
Nov 28 08:57:10 kernel: raid1: Disk failure on sda2, disabling device.
Nov 28 08:57:10 kernel: raid1: Operation continuing on 1 devices.

We're working through our changes to figure out what might have 
triggered it, but it seems likely the root cause lies in the core code.

We're assuming it's a software issue since it's reproducible on multiple 
new-ish systems, although so far we've only tried it on systems with one 
particular configuration--we're planning on trying it with different 
disks just to be sure.

For what it's worth, we've seen the problems with disk write cache 
enabled and disabled.

Anyone have any ideas, or pointers as to what I should look at?

Thanks,
Chris


-- 

Chris Friesen
Software Designer

3500 Carling Avenue
Ottawa, Ontario K2H 8E9
www.genband.com

             reply	other threads:[~2012-11-28 17:52 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-28 17:52 Chris Friesen [this message]
2012-11-28 18:08 ` getting I/O errors in super_written()...any ideas what would cause this? Mathias Burén
2012-11-28 18:51   ` Roy Sigurd Karlsbakk
2012-11-28 20:21     ` Chris Friesen
2012-11-28 20:27       ` Mathias Burén
2012-11-28 20:29         ` Chris Friesen
2012-12-03 20:22           ` Ric Wheeler
2012-12-03 20:44             ` Chris Friesen
2012-12-03 20:52               ` Ric Wheeler
2012-12-03 21:08                 ` Chris Friesen
2012-12-03 21:21                   ` Dave Jiang
2012-12-03 21:36                     ` Chris Friesen
2012-12-03 21:59                       ` Dave Jiang
2012-12-03 21:53                   ` Ric Wheeler
2012-12-04 22:00                     ` Chris Friesen
2012-12-04 23:55                       ` Ric Wheeler
2012-12-05  9:20                       ` James Bottomley
2012-12-05 11:41                         ` Ric Wheeler
2012-12-05 11:57                           ` James Bottomley
2012-12-06 18:15                         ` Chris Friesen
2012-12-06 20:27                           ` Chris Murphy
2012-12-08 18:08                           ` James Bottomley

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=50B64F51.6000402@genband.com \
    --to=chris.friesen@genband.com \
    --cc=axboe@kernel.dk \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.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.