On 01/26/2010 03:47 PM, Nikola Ciprich wrote:
Hello Theo,
Actually it's ME who appreciates YOUR efforts ;)
I'm sorry for late reply, I did a lot of testing and I've been a bit
busy lately.
It's getting quite weird. I can 100% reproduce it.
BUT - the thing is, I can reproduce it only on external eSATA box with
long eSATA cable. I've tried it on two different machines, and with
two different disk boxes. Using shorter cabling seems to fix the problem.
I'd just close the problem stating that it's caused byt crappy cable,
but what worries me is why it was working with older kernels?
Does it mean our backups were just silently being damaged and new
kernel somehow detects the problem? (and if it's the hw problem,
kernel could maybe show it the better way then just crashing).
I'm going to repeat tests with older kernels which were working
OK, and I can also test newer ones. I'll also try to get new
cable of same length to check it again.
Do You have any other ideas what else I should check?
with best regards
nik
Hi Nik,
If you only see this with an external S-ATA box and a long cable, we
might have issues with S-ATA (and knock on issues with error handling up
the stack).
Can you summarize/repost the log of the panic with the linux-ide people
cc'ed (added above)?
Thanks!
Ric
On Sun, Jan 24, 2010 at 04:48:53AM -0500, tytso@xxxxxxx wrote:
On Sun, Jan 24, 2010 at 08:19:43AM +0100, Nikola Ciprich wrote:
Hi,
yes, I can reproduce it reliably, I'll give it a try tomorrow and
report.
have a nice day.
Thanks, I appreciate it. If it does reproduce on 2.6.33-rc3+, could
you send me the output of "dumpe2fs -h /dev/XXX"?
Best regards,
- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
