From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Chris Murphy <lists@colorremedies.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: bug? fstrim only trims unallocated space, not unused in bg's
Date: Mon, 20 Nov 2017 10:13:34 +0800 [thread overview]
Message-ID: <d784d9a6-bc0e-e4c3-6633-043081ea800b@gmx.com> (raw)
In-Reply-To: <CAJCQCtRpWuPLsmGLmNcon45YzfewRFPHxjhCJY=mVZ_Od7jxxQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1965 bytes --]
On 2017年11月19日 14:17, Chris Murphy wrote:
> fstrim should trim free space, but it only trims unallocated. This is
> with kernel 4.14.0 and the entire 4.13 series. I'm pretty sure it
> behaved this way with 4.12 also.
Tested with 4.14-rc7, can't reproduce it.
------
# btrfs fi us /mnt/btrfs/
Overall:
Device size: 1.00GiB
Device allocated: 566.38MiB
Device unallocated: 457.62MiB
Device missing: 0.00B
Used: 256.81MiB
Free (estimated): 649.62MiB (min: 420.81MiB)
Data ratio: 1.00
Metadata ratio: 2.00
Global reserve: 16.00MiB (used: 0.00B)
Data,single: Size:448.00MiB, Used:256.00MiB
/dev/loop0 448.00MiB
Metadata,DUP: Size:51.19MiB, Used:400.00KiB
/dev/loop0 102.38MiB
System,DUP: Size:8.00MiB, Used:16.00KiB
/dev/loop0 16.00MiB
Unallocated:
/dev/loop0 457.62MiB
# fstrim /mnt/btrfs -v
/mnt/btrfs: 665.3 MiB (697597952 bytes) trimmed
------
Any special mount options or setup?
(BTW, I also tried space_cache=v2 and default v1, no obvious difference)
Thanks,
Qu
>
>
> [root@f27h ~]# fstrim -v /
> /: 39 GiB (41841328128 bytes) trimmed
> [root@f27h ~]# btrfs fi us /
> Overall:
> Device size: 70.00GiB
> Device allocated: 31.03GiB
> Device unallocated: 38.97GiB
> Device missing: 0.00B
> Used: 22.02GiB
> Free (estimated): 47.72GiB (min: 47.72GiB)
> Data ratio: 1.00
> Metadata ratio: 1.00
> Global reserve: 65.97MiB (used: 0.00B)
>
> Data,single: Size:30.00GiB, Used:21.25GiB
> /dev/nvme0n1p8 30.00GiB
>
> Metadata,single: Size:1.00GiB, Used:791.58MiB
> /dev/nvme0n1p8 1.00GiB
>
> System,single: Size:32.00MiB, Used:16.00KiB
> /dev/nvme0n1p8 32.00MiB
>
> Unallocated:
> /dev/nvme0n1p8 38.97GiB
>
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 520 bytes --]
next prev parent reply other threads:[~2017-11-20 2:13 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-19 6:17 bug? fstrim only trims unallocated space, not unused in bg's Chris Murphy
2017-11-19 6:27 ` Andrei Borzenkov
2017-11-19 21:38 ` Chris Murphy
[not found] ` <3114a78e-485a-daea-f8b1-48cc330f4209@suse.com>
2017-11-20 20:01 ` Jeff Mahoney
2017-11-20 20:40 ` Jeff Mahoney
2017-11-20 21:56 ` Chris Murphy
2017-11-20 22:59 ` Chris Murphy
2017-11-21 1:46 ` Jeff Mahoney
2017-11-21 4:04 ` Chris Murphy
2017-11-21 4:13 ` Jeff Mahoney
2017-11-21 4:15 ` Chris Murphy
2017-11-20 2:13 ` Qu Wenruo [this message]
2017-11-20 2:24 ` Chris Murphy
2017-11-20 2:30 ` Chris Murphy
2017-11-20 2:42 ` Qu Wenruo
2017-11-20 22:23 ` Chris Murphy
2017-11-21 1:16 ` Qu Wenruo
2017-11-21 4:06 ` Chris Murphy
2017-11-21 4:09 ` Chris Murphy
2017-11-21 4:29 ` Qu Wenruo
2017-11-21 4:34 ` Chris Murphy
2017-11-21 4:43 ` Qu Wenruo
2017-11-21 4:46 ` Chris Murphy
2017-11-21 4:49 ` Chris Murphy
2017-11-21 4:58 ` Qu Wenruo
2017-11-21 5:58 ` Chris Murphy
2017-11-21 6:10 ` Qu Wenruo
2018-04-01 3:28 ` Chris Murphy
2018-04-01 10:34 ` Qu Wenruo
2018-04-01 23:30 ` Chris Murphy
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=d784d9a6-bc0e-e4c3-6633-043081ea800b@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
/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