All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Holger Hoffstätte" <holger.hoffstaette@googlemail.com>
To: Glyn Normington <gnormington@pivotal.io>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH V2] Btrfs: keep dropped roots in cache until transaction commit
Date: Wed, 16 Sep 2015 16:48:08 +0200	[thread overview]
Message-ID: <55F98128.9060509@googlemail.com> (raw)
In-Reply-To: <CAA-6JZq+bL31eD5sxaLjwt41G68BzPjt=MJi4hTEgwvMXy3_ZA@mail.gmail.com>

Hi Glyn :)

On 09/16/15 16:31, Glyn Normington wrote:
> We are seeing a very similar problem fwiw. Unfortunately we can't
> reproduce this reliably, but it is cropping up regularly. Here's a
> chore we are using to track our work on this: [2].
> 
> Here's the kernel log:
> 
> [610194.395845] WARNING: CPU: 3 PID: 29166 at
> /build/linux-lts-vivid-BZwsXG/linux-lts-vivid-3.19.0/fs/btrfs/super.c:260
> __btrfs_abort_transaction+0x54/0x130 [btrfs]()

This is an entirely different problem and may have long been fixed;
I count at least 6 patches for tx aborts in my 4.1++ tree alone.
We're talking about patches that I can guarantee you are not running.

If Pivotal needs some help with stable btrfs backport fixes I might be
able to resurrect my old 3.19 patch queue (check my Github!), but this
is close to Zombie Olympics.. :)

cheers
Holger


  reply	other threads:[~2015-09-16 14:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-16 14:31 [PATCH V2] Btrfs: keep dropped roots in cache until transaction commit Glyn Normington
2015-09-16 14:48 ` Holger Hoffstätte [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-09-15 14:07 Josef Bacik
2015-09-15 15:50 ` Holger Hoffstätte
2015-09-15 15:56   ` Josef Bacik
2015-09-15 19:08   ` Holger Hoffstätte
2015-09-15 19:15     ` Josef Bacik
2015-09-15 19:39       ` Holger Hoffstätte
2015-09-16  8:58       ` Holger Hoffstätte
2015-09-16 13:50         ` Josef Bacik
2015-09-16 14:00           ` Holger Hoffstätte
2015-09-18 18:28           ` Omar Sandoval

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=55F98128.9060509@googlemail.com \
    --to=holger.hoffstaette@googlemail.com \
    --cc=gnormington@pivotal.io \
    --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.