All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Costaras <stevecs@chaven.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: xfs@oss.sgi.com
Subject: Re: XFS data corruption with high I/O even on hardware raid
Date: Thu, 14 Jan 2010 05:19:49 -0600	[thread overview]
Message-ID: <4B4EFDD5.5060408@chaven.com> (raw)
In-Reply-To: <87hbqpf3zv.fsf@basil.nowhere.org>


[-- Attachment #1.1: Type: text/plain, Size: 652 bytes --]

It's the current kernel for the distribution, however I take your 
point.    I did have a 2.6.28 kernel running on another system that also 
exhibited the same problem but that system has been rebuilt to 
standardize them all on 8.04.3LTS.   I am contacting Areca to see if 
they have any suggestions as well as will try a newer kernel.


On 01/14/2010 03:08, Andi Kleen wrote:
> Steve Costaras<stevecs@chaven.com>  writes:
>    
>> ============ (System)
>> (Ubuntu 8.04.3 LTS):
>> Linux loki 2.6.24-26-server #1 SMP Tue Dec 1 18:26:43 UTC 2009 x86_64 GNU/Linux
>>      
> That's a really old kernel. Perhaps try it with a newer one?
>
> -Andi
>
>    

[-- Attachment #1.2: Type: text/html, Size: 1177 bytes --]

[-- Attachment #2: Type: text/plain, Size: 121 bytes --]

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2010-01-14 11:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-14  1:11 XFS data corruption with high I/O even on hardware raid Steve Costaras
2010-01-14  2:24 ` Dave Chinner
2010-01-14  2:33   ` Steve Costaras
2010-01-15  0:52   ` XFS data corruption with high I/O even on Areca " Steve Costaras
2010-01-15  1:35     ` Dave Chinner
2010-01-15  2:15       ` Steve Costaras
2010-01-14  9:08 ` XFS data corruption with high I/O even on " Andi Kleen
2010-01-14 11:19   ` Steve Costaras [this message]
2010-01-14 11:36     ` Andi Kleen

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=4B4EFDD5.5060408@chaven.com \
    --to=stevecs@chaven.com \
    --cc=andi@firstfloor.org \
    --cc=xfs@oss.sgi.com \
    /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.