From: Chris Mason <chris.mason@oracle.com>
To: "Ian! D. Allen" <idallen@idallen.ca>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs subvolume snapshot hung in btrfs_commit_transaction
Date: Fri, 17 Dec 2010 09:52:10 -0500 [thread overview]
Message-ID: <1292597464-sup-8595@think> (raw)
In-Reply-To: <20101217044511.GD9177@idallen.ca>
Excerpts from Ian! D. Allen's message of 2010-12-16 23:45:12 -0500:
> On Thu, Dec 16, 2010 at 08:47:05PM -0500, Chris Mason wrote:
> > I think this hang is something that sage fixed. Which kernel is this
> > ubuntu including?
>
> All that detail is posted in the second message in the thread you quoted:
>
> http://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg07448.html
The 2.6.35 kernel didn't have Sage's fix. I'd say the deadlock will be
fixed in the current btrfs-unstable git tree (against 2.6.36).
>
> Is the btrfsck snapshot error (from Tuesday) fixed too?
I'm looking into that one, I think it is a btrfsck bug.
-chris
next prev parent reply other threads:[~2010-12-17 14:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-12 3:43 btrfs subvolume snapshot hung in btrfs_commit_transaction Ian! D. Allen
2010-12-12 8:14 ` Ian! D. Allen
2010-12-12 9:45 ` btrfs subvolume list fails to show all snapshots Ian! D. Allen
2010-12-13 8:47 ` Li Zefan
2011-01-20 23:01 ` Ian! D. Allen
2011-01-21 2:03 ` Li Zefan
2010-12-14 2:23 ` btrfs subvolume snapshot hung in btrfs_commit_transaction Ian! D. Allen
2010-12-17 1:47 ` Chris Mason
2010-12-17 4:45 ` Ian! D. Allen
2010-12-17 14:52 ` Chris Mason [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-12-08 14:01 Ian! D. Allen
2010-12-09 19:46 ` Ian! D. Allen
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=1292597464-sup-8595@think \
--to=chris.mason@oracle.com \
--cc=idallen@idallen.ca \
--cc=linux-btrfs@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).