From: Martin Steigerwald <Martin@lichtvoll.de>
To: Chris Mason <clm@fb.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: BTRFS hang with 3.16-rc5
Date: Fri, 18 Jul 2014 09:51:35 +0200 [thread overview]
Message-ID: <25104768.pskoHShbKc@merkaba> (raw)
In-Reply-To: <53C52AE4.6010803@fb.com>
Am Dienstag, 15. Juli 2014, 09:21:40 schrieb Chris Mason:
> 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?
On this system it is a matter.
3.16-rc5: Two hangs in one day
3.16-rc4: No hang so far with three days uptime (well with hibernation cycles
in between)
So easy observation for me: 3.16-rc4 fine, 3.16-rc5 broke.
Ciao,
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
next prev parent reply other threads:[~2014-07-18 7:51 UTC|newest]
Thread overview: 35+ 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
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 15:36 ` Nick Krause
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 ` Martin Steigerwald [this message]
2014-07-18 13:36 ` BTRFS hang with 3.16-rc5 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=25104768.pskoHShbKc@merkaba \
--to=martin@lichtvoll.de \
--cc=clm@fb.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 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.