From: Dave Chinner <david@fromorbit.com>
To: Sean Purdy <sean-kernel@purdy.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
xfs@oss.sgi.com
Subject: Re: BUG: XFS internal error xfs_trans_cancel in 2.6.27
Date: Fri, 17 Oct 2008 09:56:11 +1100 [thread overview]
Message-ID: <20081016225611.GC31761@disturbed> (raw)
In-Reply-To: <20081016151752.F30919@moloch.hellmouth.net>
On Thu, Oct 16, 2008 at 03:17:52PM +0100, Sean Purdy wrote:
> On Fri, 10 Oct 2008, Dave Chinner said:
> > On Thu, Oct 09, 2008 at 11:36:10AM +0100, Sean Purdy wrote:
> > > Hi,
> > >
> > > Further to the discussion (and patching) of an xfs_trans_cancel
> > > issue in June, in kernel < 2.6.26
> > >
> > > A similar issue came up on one disk of a 4 x 750GiB machine
> > > with a 2.6.24 kernel. So I installed 2.6.27-6 and gave it another try.
> > > But I'm still seeing the same problem. Remounting the drive each time
> > > is fine, and xfs_check shows no errors.
> >
> > 2.6.27-6? You mean 2.6.27-rc6?
>
> I meant rc9 as it happens, but never mind.
>
> > Anyway, you need to try this patch:
> >
> > http://oss.sgi.com/archives/xfs/2008-10/msg00105.html
> >
> > which I posted a few days ago that fixes the latest reproducable
> > case of this shutdown that I know of.
>
> This patch worked fine, thanks very much!
Great. It's good to know that mutliple people إve been hitting
this specific problem.
> Can we get it into
> some stable version of 2.6.27? Maybe I can put in a bug request
> for the next Ubuntu kernel.
We haven't pushed it upstream for .28-rc1 yet as it is still being
QA'd. Once it is pushed we can consider it for .27-stable.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
prev parent reply other threads:[~2008-10-16 22:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-09 10:36 BUG: XFS internal error xfs_trans_cancel in 2.6.27 Sean Purdy
2008-10-09 23:02 ` Dave Chinner
2008-10-10 9:22 ` Sean Purdy
2008-10-16 14:17 ` Sean Purdy
2008-10-16 22:56 ` 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=20081016225611.GC31761@disturbed \
--to=david@fromorbit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sean-kernel@purdy.org \
--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