From: Rich Freeman <r-btrfs@thefreemanclan.net>
To: Josef Bacik <jbacik@fb.com>
Cc: Zach Brown <zab@redhat.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Btrfs: fix deadlock with nested trans handles
Date: Wed, 12 Mar 2014 12:34:37 -0400 [thread overview]
Message-ID: <CAGfcS_ktoasT-esMTcLbF+o_-4KTirZghtJ5+o4goZDTY4DW0A@mail.gmail.com> (raw)
In-Reply-To: <53207C4B.6020000@fb.com>
On Wed, Mar 12, 2014 at 11:24 AM, Josef Bacik <jbacik@fb.com> wrote:
> On 03/12/2014 08:56 AM, Rich Freeman wrote:
>>
>> After a number of reboots the system became stable, presumably
>> whatever race condition btrfs was hitting followed a favorable
>> path.
>>
>> I do have a 2GB btrfs-image pre-dating my application of this
>> patch that was causing the issue last week.
>>
>
> Uhm wow that's pretty epic. I will talk to chris and figure out how
> we want to deal with that and send you a patch shortly. Thanks,
If you need any info from me at all beyond the capture let me know.
A tiny bit more background. The system would boot normally, but panic
after about 30-90 seconds (usually long enough to log into KDE,
perhaps even fire up a browser/etc). In single-user mode I could
mount the filesystem read-only without issue. If I mounted it
read-write (in recovery mode or normally) I'd get the panic after
about 30-60 seconds. On one occasion it seemed stable, but panicked
when I unmounted it.
I have to say that I'm impressed that it recovers at all. I'd rather
have the file system not write anything if it isn't sure it can't
write it correctly, and that seems to be the effect here. Just about
all the issues I've run into with btrfs have tended to be lockup/etc
type issues, and not silent corruption.
Rich
next prev parent reply other threads:[~2014-03-12 16:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-07 0:01 [PATCH] Btrfs: fix deadlock with nested trans handles Josef Bacik
2014-03-07 0:25 ` Zach Brown
2014-03-12 12:56 ` Rich Freeman
2014-03-12 15:24 ` Josef Bacik
2014-03-12 16:34 ` Rich Freeman [this message]
2014-03-14 22:40 ` Rich Freeman
2014-03-15 11:51 ` Duncan
2014-03-21 2:13 ` Rich Freeman
2014-03-21 5:44 ` Duncan
2014-03-17 14:34 ` Josef Bacik
2014-05-03 20:04 ` Alex Lyakas
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=CAGfcS_ktoasT-esMTcLbF+o_-4KTirZghtJ5+o4goZDTY4DW0A@mail.gmail.com \
--to=r-btrfs@thefreemanclan.net \
--cc=jbacik@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=zab@redhat.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 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.