3ware error? WTF is this?

3ware error? WTF is this?

[Robert L. Harris]

[-- Attachment #1: Type: text/plain, Size: 1170 bytes --]



Guys, I've got a machine generating all kinds of wierd errors.  It
failed 4 out of 8 drives on a 3ware card.  A reboot cleared all but 1
up, I've had alot of lag while the card is spitting errors etc.  I'm
about to launch this thing into the nearest highway I can find.

This morning I got this:

3w-xxxx: scsi1: PCI Parity Error: clearing.
EXT3-fs error (device md(9,2)): ext3_add_entry: bad entry in directory
#65: rec_len % 4 != 0 - offset=552, inode=93, rec_len=21, name_len=11
3w-xxxx: scsi2: PCI Parity Error: clearing.


Can I get an educated "oh, your card is bad" or "hmm, bad driver maybe?"
or something I can poke with a stick?  It's a brand new box with brand
new drives and controllers.  It was running great until last week.
Kernel 2.4.19 with 3ware driver 7.5.2 from their web page.

Robert


:wq!
---------------------------------------------------------------------------
Robert L. Harris                     | PGP Key ID: FC96D405
                               
DISCLAIMER:
      These are MY OPINIONS ALONE.  I speak for no-one else.
FYI:
 perl -e 'print $i=pack(c5,(41*2),sqrt(7056),(unpack(c,H)-2),oct(115),10);'


[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: 3ware error? WTF is this?

[Andre Hedrick]

Robert,

Could you give us a little more meat to chew on?
"Kernel 2.4.19 with 3ware driver 7.5.2 from their web page", firmware ??
The driver has a version string like "1.02.00.025".
"PCI Parity Error" is more or less a mainboard error, or a barrier commit
error.  I see you are doing that favorite "jbod" thing with "md" has your
raid wrapper.  Best guess, who knows but more data is useful and required.

Cheers,

Andre Hedrick
LAD Storage Consulting Group


On Tue, 28 Jan 2003, Robert L. Harris wrote:

> 
> 
> Guys, I've got a machine generating all kinds of wierd errors.  It
> failed 4 out of 8 drives on a 3ware card.  A reboot cleared all but 1
> up, I've had alot of lag while the card is spitting errors etc.  I'm
> about to launch this thing into the nearest highway I can find.
> 
> This morning I got this:
> 
> 3w-xxxx: scsi1: PCI Parity Error: clearing.
> EXT3-fs error (device md(9,2)): ext3_add_entry: bad entry in directory
> #65: rec_len % 4 != 0 - offset=552, inode=93, rec_len=21, name_len=11
> 3w-xxxx: scsi2: PCI Parity Error: clearing.
> 
> 
> Can I get an educated "oh, your card is bad" or "hmm, bad driver maybe?"
> or something I can poke with a stick?  It's a brand new box with brand
> new drives and controllers.  It was running great until last week.
> Kernel 2.4.19 with 3ware driver 7.5.2 from their web page.
> 
> Robert
> 
> 
> :wq!
> ---------------------------------------------------------------------------
> Robert L. Harris                     | PGP Key ID: FC96D405
>                                
> DISCLAIMER:
>       These are MY OPINIONS ALONE.  I speak for no-one else.
> FYI:
>  perl -e 'print $i=pack(c5,(41*2),sqrt(7056),(unpack(c,H)-2),oct(115),10);'
> 
> 

Re: 3ware error? WTF is this?

[Robert L. Harris]

[-- Attachment #1: Type: text/plain, Size: 2799 bytes --]



Sorry, Firmware is also 7.5.2 per the web page (try to keep driver and
firmware in sync so I forget to specify that sometimes).  The
configuration is 8 drives being software raid'd into 2 4drive raid5's.
When this was built we went this route as we were told that the raid5
implementation for the 3ware was slower than the software.  We didn't
have alot of time to test this theory and prove it wrong unfortunately.
We need the space of raid5 more than the reduancancy of mirroring.  

What else can I tell you?

Robert


Thus spake Andre Hedrick (andre@linux-ide.org):

> 
> Robert,
> 
> Could you give us a little more meat to chew on?
> "Kernel 2.4.19 with 3ware driver 7.5.2 from their web page", firmware ??
> The driver has a version string like "1.02.00.025".
> "PCI Parity Error" is more or less a mainboard error, or a barrier commit
> error.  I see you are doing that favorite "jbod" thing with "md" has your
> raid wrapper.  Best guess, who knows but more data is useful and required.
> 
> Cheers,
> 
> Andre Hedrick
> LAD Storage Consulting Group
> 
> 
> On Tue, 28 Jan 2003, Robert L. Harris wrote:
> 
> > 
> > 
> > Guys, I've got a machine generating all kinds of wierd errors.  It
> > failed 4 out of 8 drives on a 3ware card.  A reboot cleared all but 1
> > up, I've had alot of lag while the card is spitting errors etc.  I'm
> > about to launch this thing into the nearest highway I can find.
> > 
> > This morning I got this:
> > 
> > 3w-xxxx: scsi1: PCI Parity Error: clearing.
> > EXT3-fs error (device md(9,2)): ext3_add_entry: bad entry in directory
> > #65: rec_len % 4 != 0 - offset=552, inode=93, rec_len=21, name_len=11
> > 3w-xxxx: scsi2: PCI Parity Error: clearing.
> > 
> > 
> > Can I get an educated "oh, your card is bad" or "hmm, bad driver maybe?"
> > or something I can poke with a stick?  It's a brand new box with brand
> > new drives and controllers.  It was running great until last week.
> > Kernel 2.4.19 with 3ware driver 7.5.2 from their web page.
> > 
> > Robert
> > 
> > 
> > :wq!
> > ---------------------------------------------------------------------------
> > Robert L. Harris                     | PGP Key ID: FC96D405
> >                                
> > DISCLAIMER:
> >       These are MY OPINIONS ALONE.  I speak for no-one else.
> > FYI:
> >  perl -e 'print $i=pack(c5,(41*2),sqrt(7056),(unpack(c,H)-2),oct(115),10);'
> > 
> > 



:wq!
---------------------------------------------------------------------------
Robert L. Harris                     | PGP Key ID: FC96D405
                               
DISCLAIMER:
      These are MY OPINIONS ALONE.  I speak for no-one else.
FYI:
 perl -e 'print $i=pack(c5,(41*2),sqrt(7056),(unpack(c,H)-2),oct(115),10);'


[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]