From: Dave Chinner <david@fromorbit.com>
To: Emmanuel Florac <eflorac@intellique.com>
Cc: xfs@oss.sgi.com
Subject: Re: easily reproducible filesystem crash on rebuilding array
Date: Tue, 16 Dec 2014 07:10:36 +1100 [thread overview]
Message-ID: <20141215201036.GQ24183@dastard> (raw)
In-Reply-To: <20141215132500.13210fdb@harpe.intellique.com>
On Mon, Dec 15, 2014 at 01:25:00PM +0100, Emmanuel Florac wrote:
> Le Mon, 15 Dec 2014 13:07:15 +0100
> Emmanuel Florac <eflorac@intellique.com> écrivait:
>
> > Dec 12 00:40:18 TEST-ADAPTEC kernel: XFS (dm-0):
> > xfs_do_force_shutdown(0x1) called from line 383 of file
> > fs/xfs/xfs_trans_buf.c. Return address = 0xffffffff8125cc90
> > Dec 12 00:40:31 TEST-ADAPTEC kernel: XFS (dm-0): xfs_log_force: error
> > 5 returned.
> > Dec 12 00:41:02 TEST-ADAPTEC kernel: XFS (dm-0): xfs_log_force: error
> > 5 returned.
> >
>
> Reading the source I see that the error occured in xfs_buf_read_map, I
> suppose it's when xfsbufd tries to scan dirty metadata?
a) we don't have an xfsbufd anymore, and b) the xfsbufd never
"scanned" or read metadata - it only wrote dirty buffers back to
disk.
> This is a read
> error, so it could very well be a simple IO starvation at the controller
> level (as the controller probably gives priority to whatever writes are
> pending over reads).
The controller is broken if it's returning EIO to reads when it
is busy.
> Maybe setting xfsbufd_centisecs to the max could help here?
Deprecated Sysctls
==================
fs.xfs.xfsbufd_centisecs (Min: 50 Default: 100 Max: 3000)
Dirty metadata is now tracked by the log subsystem and
flushing is driven by log space and idling demands. The
xfsbufd no longer exists, so this syctl does nothing.
Due for removal in 3.14.
Seems like the removal patch is overdue....
> Trying
> right away... Any advice welcome.
http://xfs.org/index.php/XFS_FAQ#Q:_What_information_should_I_include_when_reporting_a_problem.3F
I'd start with upgrading the firmware on your RAID controller and
turning the XFS error level up to 11....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-12-15 20:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-11 11:39 easily reproducible filesystem crash on rebuilding array Emmanuel Florac
2014-12-11 15:52 ` Eric Sandeen
2014-12-15 12:07 ` Emmanuel Florac
2014-12-15 12:25 ` Emmanuel Florac
2014-12-15 20:10 ` Dave Chinner [this message]
2014-12-16 7:56 ` Christoph Hellwig
2014-12-16 11:38 ` Emmanuel Florac
2014-12-16 17:21 ` Emmanuel Florac
2014-12-16 11:34 ` Emmanuel Florac
2014-12-16 19:58 ` Dave Chinner
2014-12-17 11:21 ` Emmanuel Florac
2014-12-18 15:40 ` Emmanuel Florac
2014-12-18 22:58 ` Dave Chinner
2014-12-19 11:57 ` Emmanuel Florac
2014-12-19 23:06 ` Dave Chinner
2014-12-16 11:08 ` easily reproducible filesystem crash on rebuilding array [XFS bug in my book] Emmanuel Florac
2014-12-16 20:04 ` Dave Chinner
2015-01-13 11:21 ` easily reproducible filesystem crash on rebuilding array Emmanuel Florac
2015-01-13 13:59 ` Emmanuel Florac
[not found] <CAH-PCH7W4yTDRhAiKQwN_wQJMx2sTitQYrLNPcLYHvJRucXBjA@mail.gmail.com>
2015-09-17 6:17 ` Emmanuel Florac
2015-09-17 7:21 ` Ferenc Kovacs
2015-09-17 11:17 ` Emmanuel Florac
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=20141215201036.GQ24183@dastard \
--to=david@fromorbit.com \
--cc=eflorac@intellique.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox