From: Chris Murphy <lists@colorremedies.com>
To: Roman Mamedov <rm@romanrm.net>
Cc: Chris Murphy <lists@colorremedies.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: 5.5-5.6-rc1, fstrim reports different value 1 minute later
Date: Wed, 12 Feb 2020 23:28:29 -0700 [thread overview]
Message-ID: <CAJCQCtQewPT1oyDm3RASWpjtz+vr=2DdThdLeM_Thz-SeqEtLA@mail.gmail.com> (raw)
In-Reply-To: <20200213112110.7100baf2@natsu>
On Wed, Feb 12, 2020 at 11:21 PM Roman Mamedov <rm@romanrm.net> wrote:
>
> On Wed, 12 Feb 2020 23:08:03 -0700
> Chris Murphy <lists@colorremedies.com> wrote:
>
> > Host: kernel 5.5.3, qemu-kvm, Btrfs, backing file is raw with +C 5.6.
> > Guest: kernel 5.6.0-rc1, / is Btrfs
> >
> > Boot and login, and immediately run these commands:
> >
> > [root@localhost ~]# df -h
> > /dev/vda4 96G 4.4G 91G 5% /
> > # fstrim -v /
> > /: 91 GiB (97633062912 bytes) trimmed
> >
> > 1 minute later
> >
> > [root@localhost ~]# fstrim -v /
> > /: 3.5 GiB (3747549184 bytes) trimmed
> > [root@localhost ~]#
Reboot the VM with 5.5.3 and I get very slightly different values but
same behavior.
~]$ sudo -i
[sudo] password for hack:
[root@localhost ~]# fstrim -v /
/: 92.2 GiB (98953457664 bytes) trimmed
[root@localhost ~]# fstrim -v /
/: 3.7 GiB (3950542848 bytes) trimmed
[root@localhost ~]# exit
5 minutes later
$ sudo fstrim -v /
/: 3.4 GiB (3658797056 bytes) trimmed
> For completeness, what would be returned the 3rd time you trim?
I'm not seeing a pattern. Sometimes it's the same. Sometimes it's a
little different like above.
--
Chris Murphy
next prev parent reply other threads:[~2020-02-13 6:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-13 6:08 5.6-rc1, fstrim reports different value 1 minute later Chris Murphy
2020-02-13 6:21 ` Roman Mamedov
2020-02-13 6:28 ` Chris Murphy [this message]
2020-02-13 6:37 ` Chris Murphy
2020-02-13 6:51 ` Roman Mamedov
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='CAJCQCtQewPT1oyDm3RASWpjtz+vr=2DdThdLeM_Thz-SeqEtLA@mail.gmail.com' \
--to=lists@colorremedies.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=rm@romanrm.net \
/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).