Re: [Bugme-new] [Bug 14518] New: I/O appears to get stuck on certain rsync backup job and system clock halts then

[Martin Steigerwald <Martin@lichtvoll.de>]

[-- Attachment #1: Type: Text/Plain, Size: 2417 bytes --]

Am Samstag 31 Oktober 2009 schrieb Alan Cox:

[...]
> > > the machine suddenly reacted again. Later I found out that the time
> > > got stuck. The clock was going several hours to late.
> 
> If the clock gets stuck for some reason then the block layer and ATA
> timeouts are not going to work so the clock is probably the root cause.
> Clock stopped sounds like an IRQ jam, and given removing the card fixed
> it then possibly the drive jammed the IRQ on.
> 
> > > This brought some more UDMA CRC errors into the SMART LOG of my 500
> > > GB eSATA drive. Good that this is only an old age attribute.
> > > Anyway, both drives are
> 
> CRC errors are just logs of messages failing to get across uncorrupted
>  - its a sign of bad cables/power/adapters/ using SATA devices with
>  eSATA and not eSATA devices and the like. It's not really a sign of
>  drive problems.
> 
> I would say you had two problems
> 
> #1 Your eSATA cabling/power is flaky

I easily believe that for the first two occurences. As I said that eSATA 
case / cabling turned out to be quite flaky later on.

But on the third try I completely replaced it. Only thing that is 
unchanged is the 1 GB eSATA drive. But then on the third case I did not 
see *any* errors in the log at all until I disconnected both drives and 
removed the PCMCIA eSATA controller.

As of my knowing it should all be eSATA cables. I used the cables that 
where delivered with the eSATA cases.

> #2 the Cardbus Sil3512 controller somehow got stuck asserting an
> interrupt that wasn't cleared.

What could be the reason for that one? Could it be that the PCMCIA card 
had to many plug / unplug cycles. Contacts look fine tough.

> Needs the Sil3512 person to look at it. Even with flaky cabling it
>  should have either recovered cleanly or dropped the device.

Yes, thats my main concern. Why did it stuck the machine for so long?

Ok, if I can help with some test I try my best to take to time for it. I 
will wait for further instructions / questions.

For now I just assume that the data in the backup is okay and just use 
rsync periodically to update the backup - that seems to work. The data is 
a bit less important than the one on the internal drive so I hope I get 
away with this ;)

Ciao,
-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]