From: Martin Steigerwald <Martin@lichtvoll.de>
To: Chris Mason <clm@fb.com>
Cc: linux-btrfs@vger.kernel.org, Cody P Schafer <dev@codyps.com>,
Marc MERLIN <marc@merlins.org>
Subject: Re: BTRFS hang with 3.16-rc5 (and also with 3.16-rc4)
Date: Tue, 29 Jul 2014 00:57:57 +0200 [thread overview]
Message-ID: <3028943.O2kv9eKhCx@merkaba> (raw)
In-Reply-To: <53D166C6.2070403@fb.com>
Am Donnerstag, 24. Juli 2014, 16:04:22 schrieb Chris Mason:
> On 07/24/2014 02:49 PM, Martin Steigerwald wrote:
> > Am Donnerstag, 24. Juli 2014, 10:58:51 schrieb Chris Mason:
> >> On 07/23/2014 06:47 PM, Martin Steigerwald wrote:
> >>> Am Dienstag, 15. Juli 2014, 17:08:27 schrieb Martin Steigerwald:
> >>>> 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?
> >>>>
> >>>> So far for this day 3.16-rc4 behaves nicely. With 3.16-rc5 I had a
> >>>> BTRFS
> >>>> hang twice yesterday. 3.16-rc4 before also behaved nicely for several
> >>>> days
> >>>> or well about a week here.
> >>>
> >>> 3.16-rc4 now hung as well…
> >>
> >> Liu Bo has a promising patch:
> >>
> >> https://urldefense.proofpoint.com/v1/url?u=https://patchwork.kernel.org/p
> >> atch/4618421/&k=ZVNjlDMF0FElm4dQtryO4A%3D%3D%0A&r=6%2FL0lzzDhu0Y1hL9xm%2B
> >> QyA%3D%3D%0A&m=CJPREifRDOxlzhYeURx75h33LGU7YemJsNeLP%2FvXCv8%3D%0A&s=8fb0
> >> a70afce09530f16ea66a47d2af07966706b21281a7142d86256979013bab
> >>
> >> Please give it a shot. There's a second deadlock reading the free space
> >> cache, I'm still working on that one too.
> >
> > Now running 3.16-rc6 + current git + this patch.
> >
> > It may take some time tough cause during compiling the kernel BTRFS hung
> > again, which caused loss of KDE Baloo desktop search file index and parts
> > of a mail I wrote in KMail.
> >
> > Since the patch mentioned ENOSPC issues but the filesystem has enough free
> > space according to df I shrunk the trees with
>
> Thanks for giving it a try. The ENOSPC mentioned here is looking for a
> contiguous extent, so it's easily possible to trigger that enospc
> without actually being full.
So far no lockup with 3.16.0-rc6-tp520-fixcompwrite+
But BTRFS still not used up all space for laying out trees after balance:
Label: 'home' uuid: […]
Total devices 2 FS bytes used 126.70GiB
devid 1 size 160.00GiB used 156.00GiB path /dev/dm-0
devid 2 size 160.00GiB used 156.00GiB path /dev/mapper/sata-home
May be a good sign nonetheless, thus mentioned.
Any other findings?
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-28 22:58 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
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 [this message]
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=3028943.O2kv9eKhCx@merkaba \
--to=martin@lichtvoll.de \
--cc=clm@fb.com \
--cc=dev@codyps.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=marc@merlins.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).