From: Jeffrey Hundstad <jeffrey.hundstad@mnsu.edu>
To: Oliver Joa <oliver@j-o-a.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Corrupt XFS -Filesystems on new Hardware and Kernel
Date: Tue, 27 Mar 2007 14:13:27 -0500 [thread overview]
Message-ID: <46096CD7.1010100@mnsu.edu> (raw)
In-Reply-To: <46094344.4090007@j-o-a.de>
Oliver Joa wrote:
>
> I also often get a sata-bus-reset with the kernels 2.6.19.2
> and 2.6.20.2.
>
> What can I do to find the problem? I think about to change
> from xfs to ext2 but the filesystemcheck every 30 mounts lasts
> a long time.
>
> Do you have any Idea?
>
In this whole message I can only help on this point. Switching to ext2
will not help. You've got *something* wrong with YOUR setup. I have
used the kernels you mention in VERY large environments with excellent
and stable results.
You need to find out what's up with the sata-bus-reset problem. It
won't do *me* any good but people who can fix your problem will want the
entire .config and dmesg to even guess about what is going on with
*your* situation.
For more info on XFS. This is a pretty nice FAQ:
http://oss.sgi.com/projects/xfs/faq.html
--
Jeffrey Hundstad
next prev parent reply other threads:[~2007-03-27 19:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-27 16:16 Corrupt XFS -Filesystems on new Hardware and Kernel Oliver Joa
2007-03-27 19:13 ` Jeffrey Hundstad [this message]
2007-03-28 7:46 ` Oliver Joa
2007-03-28 9:30 ` Paolo Ornati
2007-03-28 10:59 ` Oliver Joa
2007-03-28 11:13 ` Paolo Ornati
2007-03-28 11:31 ` David Chinner
2007-03-28 12:42 ` Oliver Joa
2007-03-28 14:56 ` Eric Sandeen
2007-03-28 19:56 ` Oliver Joa
2007-03-29 0:21 ` Linda Walsh
2007-03-29 2:34 ` Linda Walsh
2007-03-29 9:34 ` Jan Kara
2007-03-29 11:14 ` Jens Axboe
2007-03-28 23:46 ` David Chinner
2007-03-30 13:45 ` Oliver Joa
2007-04-11 7:36 ` Oliver Joa
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=46096CD7.1010100@mnsu.edu \
--to=jeffrey.hundstad@mnsu.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=oliver@j-o-a.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox