In article <0001HW.BE232895001FCC77F04885B0@news.diapason.com >,
Georges Tomazi <gt@diapason.com> writes:
> On Sun, 30 Jan 2005 17:54:11 +0100, Peter C. Tribble wrote
> (in article <ctj3fj$f0a$1@helium.hgmp.mrc.ac.uk>):
>
>> So why did disksuite fail it?
> error message in the logs:
>
> Jan 29 22:45:40 gbr2-p40 scsi: [ID 107833 kern.warning] WARNING:
> /pci@1f,0/pci@1,1/scsi@2/sd@2,0 (sd2):
> Jan 29 22:45:40 gbr2-p40 SCSI transport failed: reason 'reset':
> retrying command
> Jan 29 22:45:48 gbr2-p40 md_stripe: [ID 641072 kern.warning] WARNING: md:
> d33: read error on /dev/dsk/c0t2d0s3
> Jan 29 22:45:48 gbr2-p40 md_mirror: [ID 842313 kern.info] NOTICE: md: d33:
> B_FAILFAST I/O retry
> Jan 29 22:46:00 gbr2-p40 md_stripe: [ID 641072 kern.warning] WARNING: md:
> d33: read error on /dev/dsk/c0t2d0s3

Looks more like a SCSI glitch rather than a disk error as such
(although then the question is - what caused the glitch? In the absence
of any other errors it's not obvious. Does iostat -E give any clues?)

>> Seems complicated. How about just
>>
>> metareplace -e d3 c0t2d0s3
>
> I tried and it worked. Thanks a lot ! Much simpler and easier than what I was
> going to do.

Good!

> So what do you think now ? Do you believe that a LVM software failure is
> something possible or the drive is definitely dying ? Is it worth breaking
> the mirror to reformat the disk and recreate the mirror ?

As I said, I would always do a format/analyze/read test.

(The resync only does writes...so isn't a full test.)

--
-Peter Tribble
MRC Rosalind Franklin Centre for Genomics Research
http://www.rfcgr.mrc.ac.uk/~ptribble/ - http://ptribble.blogspot.com/