All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ric Wheeler <rwheeler@redhat.com>
To: Nikola Ciprich <extmaillist@linuxbox.cz>
Cc: tytso@mit.edu, Nikola Ciprich <nikola.ciprich@linuxbox.cz>,
	ext4 maillist <linux-ext4@vger.kernel.org>,
	IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: 2.6.32.4 - still getting ext4 related crashes
Date: Wed, 27 Jan 2010 15:40:06 -0500	[thread overview]
Message-ID: <4B60A4A6.3070001@redhat.com> (raw)
In-Reply-To: <20100126204754.GA4637@nik-comp.linuxbox.cz>

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@mit.edu 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@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>
>>      
>    


  reply	other threads:[~2010-01-27 20:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-22  8:50 2.6.32.4 - still getting ext4 related crashes Nikola Ciprich
2010-01-22 21:38 ` tytso
2010-01-24  7:19   ` Nikola Ciprich
2010-01-24  9:48     ` tytso
2010-01-26 20:47       ` Nikola Ciprich
2010-01-27 20:40         ` Ric Wheeler [this message]
2010-01-28 17:24           ` Nikola Ciprich
2010-01-28 18:17             ` Ric Wheeler
2010-01-28 18:36               ` Nikola Ciprich
2010-02-11  2:27                 ` Tejun Heo
2010-02-15  6:13                   ` Nikola Ciprich

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B60A4A6.3070001@redhat.com \
    --to=rwheeler@redhat.com \
    --cc=extmaillist@linuxbox.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=nikola.ciprich@linuxbox.cz \
    --cc=tytso@mit.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.