From: Marc MERLIN <marc@merlins.org>
To: "Holger Hoffstätte" <holger.hoffstaette@googlemail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Fixing the btrfs deadlocks
Date: Sun, 10 Aug 2014 09:36:59 -0700 [thread overview]
Message-ID: <20140810163659.GO12778@merlins.org> (raw)
In-Reply-To: <pan.2014.08.10.15.42.09@googlemail.com>
On Sun, Aug 10, 2014 at 03:42:09PM +0000, Holger Hoffstätte wrote:
> On Sun, 10 Aug 2014 07:39:00 -0700, Marc MERLIN wrote:
>
> > My apologies if I missed some Emails, but I'm a bit confused.
> > The deadlocks happen reliably with 3.15+, but those patches are marked as
> > being for 3.14 in your URL, but then you say you didn't backport them to
> > 3.14.
>
> sigh :)
>
> My patch queue is meant for 3.14 only. The notorious hangs in 3.15+
> are a different issue, as we have seen likely caused by the workqueue
> changes; I was only interested in keeping & improving 3.14.x, precisely
> because 3.15 is still borked and short-lived, and 3.16 has exciting new,
> completely btrfs-unrelated problems for which I really don't have much
> patience at the moment.
Aaah, gotcha, and to be clear, 3.16 has the same hang problems so far
(or maybe even worse).
> I meant you could try my patch queue if you intend to use 3.14.x for a
> longer period of time since it's a longterm kernel. If and when The Great
Ok, I understand you now.
> "Simply use the latest kernel" is laughably impractical for many reasons,
> and for the majority of people it's just easier to not use btrfs at all -
> which helps nobody.
I totally agree with you on that one.
> ..which is precisely what I said and why I'm using it. :)
> That does not mean problems identified post-3.14 cannot or should not
> be patched if they are being addressed in other trees and apply easily.
Ok, I'm following you now.
So, I don't really have time to deal with potential recoveries and
restores if anything goes wrong in the next 3 weeks, and since 3.14
works well enough for me (the hangs are rare enough that I can deal with
them), I'm unfortunately going to skip on your offer.
I do appreciate the work you did and the rationale behind it very much
actually, I'm just not the right "customer" for this at the moment.
Hopefully this new thread will bring up your work again for others to
see and hopefully it will be useful to some.
Thanks
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/ | PGP 1024R/763BE901
next prev parent reply other threads:[~2014-08-10 16:37 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-08 21:35 40TB volume taking over 16 hours to mount, any ideas? Jose Ildefonso Camargo Tolosa
2014-08-09 3:38 ` Russell Coker
2014-08-09 14:32 ` Andy Smith
2014-08-09 14:58 ` Jose Ildefonso Camargo Tolosa
2014-08-09 16:06 ` Jose Ildefonso Camargo Tolosa
2014-08-09 17:01 ` Duncan
2014-08-09 18:21 ` Marc MERLIN
2014-08-10 4:03 ` Duncan
2014-08-10 12:43 ` Holger Hoffstätte
2014-08-10 14:39 ` Fixing the btrfs deadlocks Marc MERLIN
2014-08-10 15:42 ` Holger Hoffstätte
2014-08-10 16:36 ` Marc MERLIN [this message]
2014-08-09 18:38 ` 40TB volume taking over 16 hours to mount, any ideas? Jose Ildefonso Camargo Tolosa
2014-08-09 21:02 ` Jose Ildefonso Camargo Tolosa
2014-08-10 3:58 ` Jose Ildefonso Camargo Tolosa
2014-08-10 8:24 ` Duncan
2014-08-10 8:50 ` Timofey Titovets
2014-08-10 10:16 ` Duncan
2014-08-10 16:25 ` Chris Murphy
2014-08-11 21:33 ` Jose Ildefonso Camargo Tolosa
2014-08-12 4:15 ` Duncan
2014-08-12 14:24 ` Marc MERLIN
2014-08-13 2:02 ` Jose Ildefonso Camargo Tolosa
2014-08-10 4:21 ` Duncan
2014-08-10 4:57 ` Mitch Harder
2014-08-10 7:21 ` Duncan
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=20140810163659.GO12778@merlins.org \
--to=marc@merlins.org \
--cc=holger.hoffstaette@googlemail.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 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).