From: Oliver Joa <oliver@j-o-a.de>
To: linux-kernel@vger.kernel.org
Subject: Corrupt XFS -Filesystems on new Hardware and Kernel
Date: Tue, 27 Mar 2007 18:16:04 +0200 [thread overview]
Message-ID: <46094344.4090007@j-o-a.de> (raw)
Hi,
since some weeks i try to get my new hardware running:
Intel(R) Core(TM)2 CPU 6300 @ 1.86GHz
Intel DP965LT Mainboard
Seagate SATA-Harddisk in AHCI-Mode
After some hours of running or after some heavy file-i/o
(find / | cpio -padm /test) I always get a corrupted
XFS-filesystem.
I used already the following Kernels:
2.6.19.2
2.6.19.7
2.6.20.2
2.6.20.4
After xfs_repair I get damaged files in lost+found.
I read in newsgroups that the write-cache of the harddisk
should be turned of, but the messages are all very old.
Is it still true, that it should be switched of? At startup
I get the following line:
[ 6.820776] SCSI device sda: write cache: enabled, read cache:
enabled, doesn't support DPO or FUA
So I wonder if it should be on or off.
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?
Which kernel is at the moment a so called stable? Stable enough
for my hardware?
Thanks a lot
Oliver Joa
next reply other threads:[~2007-03-27 16:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-27 16:16 Oliver Joa [this message]
2007-03-27 19:13 ` Corrupt XFS -Filesystems on new Hardware and Kernel Jeffrey Hundstad
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=46094344.4090007@j-o-a.de \
--to=oliver@j-o-a.de \
--cc=linux-kernel@vger.kernel.org \
/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.