linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Mason <clm@fb.com>
To: Martin Steigerwald <Martin@lichtvoll.de>
Cc: <linux-btrfs@vger.kernel.org>
Subject: Re: BTRFS hang with 3.16-rc5
Date: Tue, 15 Jul 2014 09:21:40 -0400	[thread overview]
Message-ID: <53C52AE4.6010803@fb.com> (raw)
In-Reply-To: <29286605.flGgbBIpOj@merkaba>

On 07/14/2014 05:58 PM, Martin Steigerwald wrote:
> Am Montag, 14. Juli 2014, 16:12:22 schrieb Chris Mason:
>> On 07/14/2014 11:10 AM, Martin Steigerwald wrote:
>>> Am Montag, 14. Juli 2014, 17:04:22 schrieben Sie:
>>>> Hi!
>>>>
>>>> While with 3.16-rc3 and rc4 I didn´t have a BTRFS hang in several days of
>>>> usage, with 3-16-rc5 I had a hang again. Less than a hour since booting
>>>> it.
>>>>
>>>> Since the hang bug I and others had with 3.15 and upto 3.16-rc2 usually
>>>> didn´t happen that quickly after boot and since backtrace looks a bit
>>>> different from what I have in memory, I post this in a new thread.
>>>> See thread "Blocked tasks on 3.15.1" for a discussion of previous hang
>>>> issues.
>>>
>>> Probably good to add some basic information on the filesystem:
>> Do you have compression enabled?  I wasn't able to nail down the 3.15.1
>> hang before vacation attacked me, but I'm hoping to track it down today.
> 
> Yes. I have.
> 
> It just hung again while I was playing PlaneShift.
> 
> Back to 3.16-rc4 as rc5 seems to be broke here.

The btrfs hang you're hitting goes back to 3.15.  So 3.16-rc4 vs rc5
shouldn't be a factor.  Are you hitting other problems with 3.16?

-chris


  reply	other threads:[~2014-07-15 13:21 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-14 15:04 BTRFS hang with 3.16-rc5 Martin Steigerwald
2014-07-14 15:10 ` Martin Steigerwald
2014-07-14 17:51   ` Duncan
2014-07-14 22:03     ` Martin Steigerwald
2014-07-15  2:45       ` Duncan
2014-07-14 20:12   ` Chris Mason
2014-07-14 21:58     ` Martin Steigerwald
2014-07-15 13:21       ` Chris Mason [this message]
2014-07-15 15:08         ` Martin Steigerwald
2014-07-23 22:47           ` BTRFS hang with 3.16-rc5 (and also with 3.16-rc4) Martin Steigerwald
2014-07-24 14:58             ` Chris Mason
2014-07-24 16:24               ` Martin Steigerwald
2014-07-24 18:49               ` Martin Steigerwald
2014-07-24 20:04                 ` Chris Mason
2014-07-28 22:57                   ` Martin Steigerwald
2014-07-25  2:32                 ` Duncan
2014-07-25  3:06                   ` Nick Krause
     [not found]                     ` <20140725080244.GA31950@carfax.org.uk>
2014-07-25  9:13                       ` Hugo Mills
2014-07-28 13:20                         ` David Sterba
2014-07-25 10:07                   ` Martin Steigerwald
2014-07-25  4:51               ` Torbjørn
     [not found]                 ` <20140725092800.GC25859@localhost.localdomain>
2014-07-25 10:22                   ` Torbjørn
     [not found]                     ` <53D23AF1.9010704@skagestad.org>
2014-07-25 11:37                       ` Torbjørn
2014-07-25 16:14                         ` Torbjørn
2014-07-28 10:00                         ` Liu Bo
2014-07-28 11:11                           ` Torbjørn
2014-07-29 10:18                             ` Liu Bo
2014-07-29 15:07                               ` Torbjørn
2014-07-30  5:09                                 ` Liu Bo
2014-07-18  7:51         ` BTRFS hang with 3.16-rc5 Martin Steigerwald
2014-07-18 13:36           ` Chris Mason
2014-07-19 17:59             ` Martin Steigerwald
2014-07-19 18:39               ` Chris Mason
2014-07-19 19:00                 ` Martin Steigerwald

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=53C52AE4.6010803@fb.com \
    --to=clm@fb.com \
    --cc=Martin@lichtvoll.de \
    --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).