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 07:39:00 -0700 [thread overview]
Message-ID: <20140810143900.GB27670@merlins.org> (raw)
In-Reply-To: <pan.2014.08.10.12.43.31@googlemail.com>
On Sun, Aug 10, 2014 at 12:43:31PM +0000, Holger Hoffstätte wrote:
> On Sat, 09 Aug 2014 11:21:13 -0700, Marc MERLIN wrote:
>
> > I sure hope that deadlock patch is going to be added to the 3.16.x tree,
> > I'm not super stocked with being stuck at 3.14.
>
> Let me try to re-stoke your enthusiasm a bit :)
>
> If you are comfortable with patching your own kernel you can take
> a look at my custom patch queue, which I just put up at:
> https://github.com/hhoffstaette/kernel-patches/tree/master/3.14
> You can take only what you need, i.e. btrfs-*.
>
> These are meant to be ironed over latest stable in order. and mostly
> address "corner cases" that seem to happen infrequently, but still
> are bad enough to leave a bad taste.
>
> Unfortunately the btrfs code has changed significantly with 3.15+,
> so later patches often no longer apply at all. However the ones that do
> have been working well for me. I don't just blindly add them, but rather
> at least try to understand what they do/change.
>
> I sent out an email for comments about backporting this select set of
> patches to 3.14, but got no replies. :(
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.
You lost me :)
That said, if you'd like to me try a set of patches that applies to
3.15.latest or 3.16 to see if they stop my frequent btrfs deadlocks, I'd be
happy to.
If the patches are meant for 3.14, that's not very helpful since 3.14 is
reasonably stable for me in comparison.
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/
next prev parent reply other threads:[~2014-08-10 14:39 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 ` Marc MERLIN [this message]
2014-08-10 15:42 ` Fixing the btrfs deadlocks Holger Hoffstätte
2014-08-10 16:36 ` Marc MERLIN
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=20140810143900.GB27670@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).