All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: bo.li.liu@oracle.com
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: spinning kworker with space_cache=v2 searching for free space
Date: Sat, 12 Nov 2016 08:58:31 +0100	[thread overview]
Message-ID: <f2c219a7-993b-64ef-4bb9-5bfe352a43b4@profihost.ag> (raw)
In-Reply-To: <20161112021821.GC30930@dhcp-whq-twvpn-1-vpnpool-10-159-131-21.vpn.oracle.com>


Am 12.11.2016 um 03:18 schrieb Liu Bo:
> On Wed, Nov 09, 2016 at 09:19:21PM +0100, Stefan Priebe - Profihost AG wrote:
>> Hello,
>>
>> found this one from 2014:
>> https://patchwork.kernel.org/patch/5551651/
>>
>> it this still valid?
> 
> The space cache code doesn't change a lot, so I think the patch is still
> valid to apply(there might be some conflicts though), but I'm not sure
> if it could help the spinning case.

Thanks got it applied and will try it. Any other ideas why it's pinning
there? Free space fragmentation?

But at least on one machine there are 26TB free and it's spinning...
slowing down the performance.

Greets,
Stefan

> 
> Thanks,
> 
> -liubo
>>
>> Am 09.11.2016 um 09:09 schrieb Stefan Priebe - Profihost AG:
>>> Dear list,
>>>
>>> even there's a lot of free space on my disk:
>>>
>>> # df -h /vmbackup/
>>> Filesystem                    Size  Used Avail Use% Mounted on
>>> /dev/mapper/stripe0-backup   37T   24T   13T  64% /backup
>>>
>>> # btrfs filesystem df /backup/
>>> Data, single: total=23.75TiB, used=22.83TiB
>>> System, DUP: total=8.00MiB, used=3.94MiB
>>> Metadata, DUP: total=283.50GiB, used=105.82GiB
>>> GlobalReserve, single: total=512.00MiB, used=0.00B
>>>
>>> I always have a kworker process endless spinning.
>>>
>>> # perf top shows:
>>>   47,56%  [kernel]               [k] rb_next
>>>    7,71%  [kernel]               [k] tree_search_offset.isra.25
>>>    6,44%  [kernel]               [k] btrfs_find_space_for_alloc
>>>
>>> Mount options:
>>> rw,noatime,compress-force=zlib,nossd,noacl,space_cache=v2,skip_balance
>>>
>>> What's wrong here?
>>>
>>> Greets,
>>> Stefan
>>>

  reply	other threads:[~2016-11-12  7:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-09  8:09 spinning kworker with space_cache=v2 searching for free space Stefan Priebe - Profihost AG
2016-11-09 20:19 ` Stefan Priebe - Profihost AG
2016-11-12  2:18   ` Liu Bo
2016-11-12  7:58     ` Stefan Priebe - Profihost AG [this message]
2016-11-12 17:23       ` Jean-Denis Girard

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=f2c219a7-993b-64ef-4bb9-5bfe352a43b4@profihost.ag \
    --to=s.priebe@profihost.ag \
    --cc=bo.li.liu@oracle.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.