From: Eric Sandeen <sandeen@sandeen.net>
To: "Rhorer, Leslie" <Leslie.Rhorer@level3.com>,
"'lrhorer@mygrande.net'" <lrhorer@mygrande.net>,
"xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: XFS File system in trouble
Date: Sat, 18 Jul 2015 10:16:46 -0400 [thread overview]
Message-ID: <55AA5FCE.4080702@sandeen.net> (raw)
In-Reply-To: <03864DDC681E664EBF5D47682BE7D7CF0D3574DF@USADCWVEMBX07.corp.global.level3.com>
On 7/17/15 9:46 PM, Rhorer, Leslie wrote:
> I have a 24T XFS file system that is very sick, and seemingly getting
> sicker. I believe it to be the file system itself. I have replaced
> the RAID chassis, the OS, the cables, the drive controller, and most
> of the drives. Re-syncing the RAID array complete in a reasonable
> time, given the size of the array, and reports no mismatches.
> Xfs_repair completes, usually with no errors found, or sometimes one
> or two errors. Some commands, like a df, are now hanging. Writes are
> often failing with I/O errors. I haven't found any amount of obvious
> file corruption, but performing a CRC check using md5sum, md6sum,
> sha256sum, etc., come up with different values every time they are
> run on many large files. What can I do to try to rectify this?
If writes fail with I/O errors, that should show up in dmesg, but I don't
see any such messages.
What did repair find?
Not a lot to go on from the above narrative, I'm afraid. What large
files are those? I presume that you are sure they should not be changing?
Thanks for all the info below...
>From the dmesg, every stuck process is stuck on nfs - doesn't look xfs
related at all.
Doesn't seem like an xfs problem, TBH, but maybe you can provide xfs_repair
output and/or dmesg when writes fail, that might offer a clue.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-07-18 14:16 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-18 1:46 XFS File system in trouble Rhorer, Leslie
2015-07-18 14:16 ` Eric Sandeen [this message]
2015-07-18 17:23 ` Rhorer, Leslie
2015-07-18 17:47 ` Kris Rusocki
2015-07-18 18:12 ` Leslie Rhorer
2015-07-19 1:02 ` Leslie Rhorer
2015-07-19 23:27 ` Dave Chinner
2015-07-20 7:41 ` Leslie Rhorer
2015-07-20 8:05 ` Martin Papik
2015-07-20 8:35 ` Leslie Rhorer
2015-07-20 8:52 ` Martin Papik
2015-07-20 13:08 ` Gim Leong Chin
2015-07-20 13:34 ` Eric Sandeen
2015-07-23 3:18 ` Eric Sandeen
2015-07-24 13:47 ` Leslie Rhorer
2015-07-24 14:44 ` Eric Sandeen
2015-07-24 15:29 ` Rhorer, Leslie
2015-07-20 11:17 ` Brian Foster
2015-07-23 1:45 ` Leslie Rhorer
2015-07-23 11:36 ` Brian Foster
2015-07-28 7:46 ` Leslie Rhorer
2015-07-28 8:35 ` Stefan Ring
2015-07-28 10:48 ` Roger Willcocks
2015-07-28 12:33 ` Brian Foster
2015-07-28 15:13 ` Leslie Rhorer
2015-07-28 16:53 ` Eric Sandeen
2015-07-28 19:12 ` Martin Papik
2015-07-28 19:52 ` Martin Steigerwald
2015-07-28 22:11 ` Brian Foster
2015-08-02 20:24 ` Leslie Rhorer
2015-08-04 7:52 ` Leslie Rhorer
2015-08-04 12:19 ` Brian Foster
2015-08-04 22:42 ` Dave Chinner
2015-08-10 1:37 ` Leslie Rhorer
2015-08-13 6:21 ` Leslie Rhorer
2015-08-14 1:26 ` Dave Chinner
2015-08-14 23:12 ` Leslie Rhorer
2015-08-15 12:28 ` Roger Willcocks
2015-08-15 18:48 ` Eric Sandeen
2015-08-15 18:57 ` Roger Willcocks
2015-08-15 22:48 ` Dave Chinner
2015-08-15 19:00 ` Eric Sandeen
2015-08-15 19:13 ` Roger Willcocks
2015-08-16 0:32 ` Eric Sandeen
2015-08-18 2:14 ` Dave Chinner
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=55AA5FCE.4080702@sandeen.net \
--to=sandeen@sandeen.net \
--cc=Leslie.Rhorer@level3.com \
--cc=lrhorer@mygrande.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox