linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Blocked tasks on 3.15.1
Date: Thu, 7 Aug 2014 16:05:13 +0000 (UTC)	[thread overview]
Message-ID: <pan$761fe$70080dc7$7b88b5e9$aef75aea@cox.net> (raw)
In-Reply-To: CAGwxe4iMg5fL=Ao5_7o86JTuXs0ttF3YsyBj+D-t_5+sBy8KAw@mail.gmail.com

Tobias Holst posted on Thu, 07 Aug 2014 17:12:17 +0200 as excerpted:

> Is there anything new on this topic? I am using Ubuntu 14.04.1 and
> experiencing the same problem.
> - 6 HDDs - LUKS on every HDD - btrfs RAID6 over this 6 crypt-devices No
> LVM, no nodatacow files.
> Mount-options: defaults,compress-force=lzo,space_cache With the original
> 3.13-kernel (3.13.0-32-generic) it is working fine.

I see you're using compress-force.  See the recent replies to the
"Btrfs: fix compressed write corruption on enospc" thread.

I'm not /sure/ your case is directly related (tho the kworker code is 
pretty new and 3.13 may be working for you due to being before the 
migration to kworkers, supporting the case of it being either the same 
problem or another related to it), but that's certainly one problem 
they've recently traced down... to a bug in the kworker threads code, 
that starts a new worker that can race with the first instead of obeying 
a flag that says keep it on the first worker.

Looks like they're doing patch that takes a slower but safer path to work 
around the kworker bug for now, as that bug was just traced (there was 
another bug, with a patch available originally hiding the ultimate 
problem, but obviously that's only half the fix as it simply revealed 
another bug underneath) and fixing it properly is likely to take some 
time.  Now that it's basically traced the workaround patch should be 
published on-list shortly and should make it into 3.17 and back into the 
stables, altho I'm not sure it'll make it into 3.16.1, etc.

But there's certainly progress. =:^)

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman


  reply	other threads:[~2014-08-07 16:05 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-27 10:02 Blocked tasks on 3.15.1 Tomasz Chmielewski
2014-06-27 13:06 ` Duncan
2014-06-27 15:14   ` Rich Freeman
2014-06-27 15:52     ` Chris Murphy
2014-06-27 17:20       ` Duncan
2014-06-28  0:22         ` Chris Samuel
2014-06-29 20:02           ` Cody P Schafer
2014-06-29 22:22             ` Cody P Schafer
2014-06-30 18:11             ` Chris Mason
2014-06-30 18:30               ` Chris Mason
2014-06-30 23:42                 ` Cody P Schafer
2014-07-01 21:04                   ` Chris Mason
2014-07-01 23:05                     ` Cody P Schafer
2014-07-02 12:27                       ` Cody P Schafer
2014-07-02 13:58                         ` Chris Mason
2014-07-02 14:15                           ` Chris Mason
2014-07-17 13:18                             ` Chris Mason
2014-07-19  0:33                               ` Blocked tasks on 3.15.1, raid1 btrfs is no ends of trouble for me Marc MERLIN
2014-07-19  0:44                                 ` Marc MERLIN
2014-07-19  1:58                                   ` Marc MERLIN
2014-07-19  1:59                                   ` Chris Samuel
2014-07-19  5:40                                     ` Marc MERLIN
2014-07-19 17:38                               ` Blocked tasks on 3.15.1 Cody P Schafer
2014-07-19 18:23                                 ` Martin Steigerwald
2014-07-22 14:53                                   ` Chris Mason
2014-07-22 15:14                                     ` Torbjørn
2014-07-22 16:46                                     ` Marc MERLIN
2014-07-22 19:42                                     ` Torbjørn
2014-07-22 19:50                                       ` Chris Mason
2014-07-22 20:10                                         ` Torbjørn
2014-07-22 21:13                                     ` Martin Steigerwald
2014-07-22 21:15                                       ` Chris Mason
2014-07-23 11:13                                         ` Martin Steigerwald
2014-07-23  1:06                                     ` Rich Freeman
2014-07-23  6:38                                       ` Felix Seidel
2014-07-23 13:20                                     ` Charles Cazabon
2014-07-25  2:27                                     ` Cody P Schafer
2014-08-07 15:12                                       ` Tobias Holst
2014-08-07 16:05                                         ` Duncan [this message]
2014-08-12  2:55                                     ` Charles Cazabon
2014-08-12  2:56                                       ` Liu Bo
2014-08-12  4:18                                         ` Duncan
2014-08-12  4:49                                       ` Marc MERLIN
2014-08-18 20:34                                         ` James Cloos
2014-07-01  3:06               ` Charles Cazabon
2014-06-30  2:33           ` Rich Freeman
2014-06-27 18:33       ` Rich Freeman
  -- strict thread matches above, loose matches on Subject: below --
2014-07-20 21:34 Matt
2014-06-27  1:37 Rich Freeman

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='pan$761fe$70080dc7$7b88b5e9$aef75aea@cox.net' \
    --to=1i5t5.duncan@cox.net \
    --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).