From: Blair Zajac <blair@orcaware.com>
To: dsterba@suse.cz
Cc: linux-btrfs@vger.kernel.org, chris.mason@fusionio.com,
jbacik@fusionio.com
Subject: Re: v3.8-rc6: btrfs-transacti Tainted: GF in btrfs_orphan_commit_root
Date: Thu, 21 Feb 2013 00:07:38 -0800 [thread overview]
Message-ID: <5125D5CA.3030301@orcaware.com> (raw)
In-Reply-To: <20130211130803.GO12339@twin.jikos.cz>
On 02/11/2013 05:08 AM, David Sterba wrote:
> On Sat, Feb 09, 2013 at 11:21:16AM -0800, Blair Zajac wrote:
>> Running an Ubuntu Raring VM which was built a week ago that is now running
>> 3.8-rc6, I was booting it last night when it hung. After a few forced
>> reboots, it came back up and I found the attached in kern.log.
>>
>> Are these reports useful? Is there any additional information I can provide
>> from the VM? What happens if it gets hung again, is there additional
>> information I can gather?
>
> Yes they're useful, we can see if it's a known or new issue. I've hit
> the same problem not so long ago and a guy on IRC reported the same
> problem yesterday.
>
> There's a fix from Josef, https://patchwork.kernel.org/patch/2083101/
> and given the increasing number of reports (the warning followed by a
> crash), I think this this a material for a late -rc.
>
> Chris please consider picking this patch for 3.8. I think it qualifies
> as a regression sice we haven't hit earlier than 3.8-rc4.
Looking at the v3.8 tag, it doesn't look like it made it in.
Since I ran into this issue on a week old VM, is it possible for this
patch to make its way into 3.8.1, so it'll be picked up by Ubuntu
automatically?
Thanks,
Blair
prev parent reply other threads:[~2013-02-21 8:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-09 19:21 v3.8-rc6: btrfs-transacti Tainted: GF in btrfs_orphan_commit_root Blair Zajac
2013-02-11 13:08 ` David Sterba
2013-02-21 8:07 ` Blair Zajac [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=5125D5CA.3030301@orcaware.com \
--to=blair@orcaware.com \
--cc=chris.mason@fusionio.com \
--cc=dsterba@suse.cz \
--cc=jbacik@fusionio.com \
--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 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.