Re: getting I/O errors in super_written()...any ideas what would cause this?

[Roy Sigurd Karlsbakk <roy@karlsbakk.net>]

> > 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?
>
> Hi,
> 
> It would be interesting to see what SMART says about the above, sinde
> the error is regarding sda first, then md follows.
>

Agreed - run smartctl -H /dev/sda or smartctl -a /dev/sda if -H succeeds
 
Vennlige hilsener / Best regards

roy
--
Roy Sigurd Karlsbakk
(+47) 98013356
roy@karlsbakk.net
http://blogg.karlsbakk.net/
GPG Public key: http://karlsbakk.net/roysigurdkarlsbakk.pubkey.txt
--
I all pedagogikk er det essensielt at pensum presenteres intelligibelt. Det er et elementært imperativ for alle pedagoger å unngå eksessiv anvendelse av idiomer med xenotyp etymologi. I de fleste tilfeller eksisterer adekvate og relevante synonymer på norsk.
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html