From: Martin Steigerwald <martin@lichtvoll.de>
To: Zygo Blaxell <zblaxell@furryterror.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: 3.19-rc5: Bug 91911: [REGRESSION] rm command hangs big time with deleting a lot of files at once
Date: Sat, 24 Jan 2015 11:20 +0100 [thread overview]
Message-ID: <6466291.Yc27r3pZsf@merkaba> (raw)
In-Reply-To: <20150123232934.GA14858@hungrycats.org>
[-- Attachment #1: Type: text/plain, Size: 1793 bytes --]
Am Freitag, 23. Januar 2015, 18:29:40 schrieb Zygo Blaxell:
> On Fri, Jan 23, 2015 at 03:01:28PM +0100, Martin Steigerwald wrote:
> > Hi!
> >
> > Anyone seen this?
> >
> > Reported as:
> >
> > https://bugzilla.kernel.org/show_bug.cgi?id=91911
>
> I have seen something like this since 3.15.
>
> I've also seen its cousin, which gets stuck in evict_inode, but the
> stacks of the hanging processes start from renameat2() instead of
> unlinkat(). I haven't seen the renameat2() variant of this bug since
> 3.18-rc6.
I see.
Well than it is at least not only happening here. So we have some more
BTRFS getting stuck issues. And this hangs happened here with BTRFS still
being able to allocate some hungs and there is also no kworker kthread at
100% of one core, so this is a different issue.
> > I just want to get rid of some 127000+ akonadi lost+found files, any
> > delete command I start just gets rid of some thousands and then
> > hangs.
> > merkaba:~> btrfs fi df /home
> > Data, RAID1: total=160.92GiB, used=111.09GiB
> > System, RAID1: total=32.00MiB, used=48.00KiB
> > Metadata, RAID1: total=5.99GiB, used=2.49GiB
> > GlobalReserve, single: total=512.00MiB, used=0.00B
> > merkaba:~> btrfs fi sh /home
> > Label: 'home' uuid: […]
> > Total devices 2 FS bytes used 113.58GiB
> > devid 1 size 170.00GiB used 166.94GiB path
> > /dev/mapper/msata-home
> > devid 2 size 170.00GiB used 166.94GiB path
> > /dev/mapper/sata-home
> > Btrfs v3.18
Also there is a lot of free space inside the allocated chunks.
[… description + dmesg as in bug report linked above …]
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2015-01-24 10:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-23 14:01 3.19-rc5: Bug 91911: [REGRESSION] rm command hangs big time with deleting a lot of files at once Martin Steigerwald
2015-01-23 14:38 ` Holger Hoffstätte
2015-01-23 14:56 ` Chris Mason
2015-01-24 14:14 ` Martin Steigerwald
2015-01-26 4:42 ` Zygo Blaxell
2015-01-23 23:29 ` Zygo Blaxell
2015-01-24 10:20 ` Martin Steigerwald [this message]
2015-01-25 22:14 ` Zygo Blaxell
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=6466291.Yc27r3pZsf@merkaba \
--to=martin@lichtvoll.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=zblaxell@furryterror.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.