From: Christoph Hellwig <hch@infradead.org>
To: Stuart Sheldon <stu@actusa.net>
Cc: support@actusa.net, xfs@oss.sgi.com
Subject: Re: Kernel crash with >2.6.28.10 + drbd + nfs + xfs + heartbeat
Date: Wed, 19 Aug 2009 14:20:49 -0400 [thread overview]
Message-ID: <20090819182049.GA10787@infradead.org> (raw)
In-Reply-To: <4A8C37F3.90300@actusa.net>
On Wed, Aug 19, 2009 at 10:35:47AM -0700, Stuart Sheldon wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> Hi all,
>
> I've traced this down to what looks to be a XFS problem. When executing
> a hb_standby the system crashes with the following error on the console:
Known problem. Fixed in latest mainline, and
http://bugzilla.kernel.org/show_bug.cgi?id=13375 has backports for
2.6.29 and 2.6.30. I will send them to 2.6.30-stable this week, but
there is no 2.6.29-stable anymore.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-08-19 18:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-19 17:35 Kernel crash with >2.6.28.10 + drbd + nfs + xfs + heartbeat Stuart Sheldon
2009-08-19 18:20 ` Christoph Hellwig [this message]
2009-08-19 18:35 ` Stuart Sheldon
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=20090819182049.GA10787@infradead.org \
--to=hch@infradead.org \
--cc=stu@actusa.net \
--cc=support@actusa.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