From: Andrea Gelmini <andrea.gelmini@gelma.net>
To: Chris Murphy <lists@colorremedies.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: fstrim is takes a long time on Btrfs and NVMe
Date: Sat, 21 Dec 2019 09:38:00 +0100 [thread overview]
Message-ID: <20191221083800.GA85226@glet> (raw)
In-Reply-To: <CAJCQCtTQ-xkWtSzXd14hb1bmozg3U8H2pxQMO7PqEJjymCcCGA@mail.gmail.com>
On Fri, Dec 20, 2019 at 11:24:24PM -0700, Chris Murphy wrote:
> Hi,
>
> Recent kernels, I think since 5.1 or 5.2, but tested today on 5.3.18,
> 5.4.5, 5.5.0rc2, takes quite a long time for `fstrim /` to complete,
> just over 1 minute.
Same effect here, since more than one year (and all update kernel
version).
It happens with my laptop devices:
nvme: KBG30ZMT128G TOSHIBA 1 128,04 GB / 128,04 GB 512 B + 0 B (Firm. 0108ADLA)
SSD sata: Samsung SSD 860 EVO 4TB (Firmw. RVT02B6Q)
I guess it doesn't matter, anyway:
nvme: btrfs
ssd: ext4 on cryptsetup + lvm
Ciao,
Gelma
next prev parent reply other threads:[~2019-12-21 8:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-21 6:24 fstrim is takes a long time on Btrfs and NVMe Chris Murphy
2019-12-21 8:38 ` Andrea Gelmini [this message]
2019-12-21 9:27 ` Nikolay Borisov
2019-12-22 3:43 ` Chris Murphy
2019-12-22 3:59 ` Chris Murphy
2019-12-22 10:40 ` Nikolay Borisov
2019-12-22 17:43 ` Josef Bacik
2019-12-22 17:49 ` Nikolay Borisov
2019-12-22 18:00 ` Josef Bacik
2019-12-22 18:06 ` Nikolay Borisov
2019-12-22 19:08 ` Chris Murphy
2019-12-22 19:15 ` Roman Mamedov
2019-12-22 22:11 ` Chris Murphy
2019-12-22 22:29 ` Nikolay Borisov
2019-12-22 23:14 ` Chris Murphy
2019-12-22 23:23 ` Chris Murphy
2019-12-22 18:50 ` 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=20191221083800.GA85226@glet \
--to=andrea.gelmini@gelma.net \
--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