From: Christoph Hellwig <hch@infradead.org>
To: stefanx <stefanx@lrz.uni-muenchen.de>
Cc: xfs@oss.sgi.com
Subject: Re: __write_lock_failed
Date: Mon, 9 May 2011 10:18:46 -0400 [thread overview]
Message-ID: <20110509141846.GG12262@infradead.org> (raw)
In-Reply-To: <4DC3E566.8070601@lrz.uni-muenchen.de>
On Fri, May 06, 2011 at 02:11:18PM +0200, stefanx wrote:
>
> Hello,
>
> some of my virtual machines (kvm/qemu) sometimes crash (xfs, Ubuntu 10.04, 2.6.32-31-x86_64).
> I think it happens while taking LVM-snapshots from the XFS-Filesystem of that machines:
This area has gotten a lot of changes since 2.6.32, including removing
the lock that's causing softlockups for you. I don't think there's much
of a chance for help with a kernel that old as people's minds have moved
on to much more recent codebases.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2011-05-09 14:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-06 12:11 __write_lock_failed stefanx
2011-05-09 14:18 ` Christoph Hellwig [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=20110509141846.GG12262@infradead.org \
--to=hch@infradead.org \
--cc=stefanx@lrz.uni-muenchen.de \
--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