From: Dave Chinner <david@fromorbit.com>
To: Simon Kirby <sim@hostway.ca>
Cc: xfs@oss.sgi.com
Subject: Re: Assertion fail in xfs_reclaim_inode [2.6.33.2]
Date: Tue, 6 Apr 2010 13:54:52 +1000 [thread overview]
Message-ID: <20100406035452.GC11036@dastard> (raw)
In-Reply-To: <20100406004730.GB11263@hostway.ca>
On Mon, Apr 05, 2010 at 05:47:30PM -0700, Simon Kirby wrote:
> We're seeing crashing from XFS likely resulting from some storage
> corruption. This seems to be getting tickled from backups every two
> days as it happens at the same time of day each time on whichever box
> is active for these storage volumes. We've seen it about 4 times now.
>
> This was captured over a serial console over IPMI serial-over-LAN, and
> it seemed the serial console loglevel was not low enough to see the
> priority-less printk() in assfail() in fs/xfs/support/debug.c, so all we
> got this time was this backtrace:
.....
>
> Seems to be from the only assert in xfs_reclaim_inode:
>
> ASSERT_ALWAYS(__xfs_iflags_test(ip, XFS_IRECLAIMABLE));
>
> Would any of the patches in the stable queue-2.6.32 be missing from
> 2.6.33 but perhaps fix this issue?
Yes, there is - commit f1f724e4b523d444c5a598d74505aefa3d6844d2.
I've been a bit slack in doing the backport and push to 2.6.33.x.
I'll get the ball rolling later this afternoon....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2010-04-06 3:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-06 0:47 Assertion fail in xfs_reclaim_inode [2.6.33.2] Simon Kirby
2010-04-06 3:54 ` 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=20100406035452.GC11036@dastard \
--to=david@fromorbit.com \
--cc=sim@hostway.ca \
--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 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.