All of lore.kernel.org
 help / color / mirror / Atom feed
From: Piotr Nowojski <piotr.nowojski@adocean-global.com>
To: Zach Brown <zab@zabbo.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: BTRFS deadlock (btrfs_join_transaction?)
Date: Wed, 23 Jan 2013 12:30:00 +0100	[thread overview]
Message-ID: <50FFC9B8.1020605@adocean-global.com> (raw)
In-Reply-To: <20130122195154.GB14246@lenny.home.zabbo.net>

W dniu 22.01.2013 20:51, Zach Brown pisze:
> It doesn't look like there's any easy answers in the code: no unbalanced
> lock and unlocks and nothing scary done while holding the lock.  (Some
> list traversal, but the traces don't show another cpu stuck spinning on
> a corrupt list).
>
> If I had to guess, I'd guess that the lock got corrupted somehow.  Maybe
> a race that has delayed work run on a freed structure.
>
> Would it be possible to enable some debugging options in the kernel
> you're building?   DEBUG_LIST, DEBUG_SPINLOCK, and the various lockdep
> options (DEBUG_LOCKDEP, PROVE_LOCKING) might raise an alarm that would
> shed some light.  Hopefully they wouldn't be unusably slow.
>
> - z
We will try to give it a shot. But it might be hard to reproduce. This 
problem occurred only once, after one week of very heavy (over)stress 
tests. Is it at least possible to confirm, that this is definitely the 
BTRFS problem?

Piotr

  reply	other threads:[~2013-01-23 11:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-22 16:52 BTRFS deadlock (btrfs_join_transaction?) Piotr Nowojski
2013-01-22 19:51 ` Zach Brown
2013-01-23 11:30   ` Piotr Nowojski [this message]
2013-01-23 18:34     ` Zach Brown

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=50FFC9B8.1020605@adocean-global.com \
    --to=piotr.nowojski@adocean-global.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=zab@zabbo.net \
    /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.