Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Jeff Mahoney <jeffm@suse.com>
To: Chris Murphy <lists@colorremedies.com>,
	Andrei Borzenkov <arvidjaar@gmail.com>
Cc: 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 15:01:17 -0500	[thread overview]
Message-ID: <bbab87ad-b84e-2bca-5d90-47a77abd295d@suse.com> (raw)
In-Reply-To: <3114a78e-485a-daea-f8b1-48cc330f4209@suse.com>


[-- Attachment #1.1: Type: text/plain, Size: 1061 bytes --]

On 11/20/17 3:00 PM, Jeff Mahoney wrote:
> On 11/19/17 4:38 PM, Chris Murphy wrote:
>> On Sat, Nov 18, 2017 at 11:27 PM, Andrei Borzenkov <arvidjaar@gmail.com> wrote:
>>> 19.11.2017 09:17, Chris Murphy пишет:
>>>> 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.
>>>>
>>>
>>> Well, I was told it should also trim free space ...
>>>
>>> https://www.spinics.net/lists/linux-btrfs/msg61819.html
>>>
>>
>> It definitely isn't. If I do a partial balance, then fstrim, I get a
>> larger trimmed value, corresponding exactly to unallocated space.
> 
> 
> I've just tested with 4.14 and it definitely trims within block groups.

Derp.  This should read 4.12.

> I've attached my test script and the log of the run.  I'll build and
> test a 4.14 kernel and see if I can reproduce there.  It may well be
> that we're just misreporting the bytes trimmed.
> 
> -Jeff
> 
> 


-- 
Jeff Mahoney
SUSE Labs


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 854 bytes --]

  parent reply	other threads:[~2017-11-20 20:01 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 [this message]
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
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=bbab87ad-b84e-2bca-5d90-47a77abd295d@suse.com \
    --to=jeffm@suse.com \
    --cc=arvidjaar@gmail.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