From: Dave Chinner <david@fromorbit.com>
To: Chandler <admin@genome.arizona.edu>
Cc: linux-xfs@vger.kernel.org
Subject: Re: Filesystem crash
Date: Mon, 4 Dec 2017 09:03:59 +1100 [thread overview]
Message-ID: <20171203220359.GW5858@dastard> (raw)
In-Reply-To: <3f4d2b55-9dd1-bc5a-2e49-cdfdc9a134b3@genome.arizona.edu>
On Fri, Dec 01, 2017 at 03:35:07PM -0700, Chandler wrote:
> Hi, we had our filesystem crash the other day after getting 100%
> full (although 53GB were still reported free). I had to reboot the
> system and use xfs_repair.
Yup, it tripped over an freespace tree corruption and shut down to
prevent it from being propagatd. Could have been caused by anything
- hardware, kernel memory corruption, a bug, a MD rebuild issue,
etc. Did you save the output of xfs_repair so we can see what errors
it fixed up?
> It seem to me this shouldn't happen just
> because it got full, so maybe there is some other issue? The
> filesystem resides on an MD RAID-5 array with 4x 2TB disks that are
> in good health, the array gets checked weekly by mdadm. The only
> error messages in the system log were related to XFS (see below).
> The OS is RHEL 6.9 with kernel 2.6.32-642.11.1.el6.x86_64.
Not much we can do to diagnose the problem on old RHEL kernels on
upstream lists - the codebase has diverged from upstream too far.
Report the problem to your local RHEL support engineer if you need
further diagnostic help.
Cheers.
Dave.
--
Dave Chinner
david@fromorbit.com
prev parent reply other threads:[~2017-12-03 22:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-01 22:35 Filesystem crash Chandler
2017-12-03 22:03 ` Dave Chinner [this message]
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=20171203220359.GW5858@dastard \
--to=david@fromorbit.com \
--cc=admin@genome.arizona.edu \
--cc=linux-xfs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).