From: Andi Kleen <andi@firstfloor.org>
To: Steve Costaras <stevecs@chaven.com>
Cc: xfs@oss.sgi.com
Subject: Re: XFS data corruption with high I/O even on hardware raid
Date: Thu, 14 Jan 2010 10:08:20 +0100 [thread overview]
Message-ID: <87hbqpf3zv.fsf@basil.nowhere.org> (raw)
In-Reply-To: <4B4E6F3F.1090901@chaven.com> (Steve Costaras's message of "Wed, 13 Jan 2010 19:11:27 -0600")
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
--
ak@linux.intel.com -- Speaking for myself only.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-01-14 9:07 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 ` Andi Kleen [this message]
2010-01-14 11:19 ` XFS data corruption with high I/O even on " Steve Costaras
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=87hbqpf3zv.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=stevecs@chaven.com \
--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.