From: Demi Marie Obenour <demi@invisiblethingslab.com>
To: Gionatan Danti <g.danti@assyoma.it>
Cc: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Running thin_trim before activating a thin pool
Date: Mon, 31 Jan 2022 14:04:15 -0500 [thread overview]
Message-ID: <YfgywUaJVsygv487@itl-email> (raw)
In-Reply-To: <b3127b95f8c2e687b4358ec0558cdd6a@assyoma.it>
[-- Attachment #1.1: Type: text/plain, Size: 1109 bytes --]
On Mon, Jan 31, 2022 at 06:54:48PM +0100, Gionatan Danti wrote:
> Il 2022-01-31 16:28 Demi Marie Obenour ha scritto:
> > thin_trim is a userspace tool that works on an entire thin pool, and I
> > suspect it may be significantly faster than blkdiscard of an individual
> > thin volume. That said, what I would *really* like is something
> > equivalent to fstrim for thin volumes: a tool that works asynchronously,
> > in the background, without disrupting concurrent I/O.
>
> Are you sure that fstrim works asynchronously?
> I remember "fstrim -v /mybigdevice" tacking some time (~30s).
It’s happens online and without preventing other I/O from happening,
whereas thin_trim can only be run offline.
> > FYI, you might want to specify a full fingerprint here; short key IDs
> > are highly vulnerable to collision and preimage attacks.
>
> Yeah, it is a 15 years old signature I must decide to update ;)
> Thanks.
Might want to generate a new key while you are at it :) (especially if
the old one is weak)
--
Sincerely,
Demi Marie Obenour (she/her/hers)
Invisible Things Lab
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 201 bytes --]
_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://listman.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
next prev parent reply other threads:[~2022-01-31 19:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-29 17:45 [linux-lvm] Running thin_trim before activating a thin pool Demi Marie Obenour
2022-01-31 11:02 ` Gionatan Danti
2022-01-31 13:41 ` Zdenek Kabelac
2022-01-31 14:12 ` Gionatan Danti
2022-01-31 15:28 ` Demi Marie Obenour
2022-01-31 17:54 ` Gionatan Danti
2022-01-31 19:04 ` Demi Marie Obenour [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-01-29 18:52 Demi Marie Obenour
2022-01-29 19:42 ` Zdenek Kabelac
2022-01-29 20:09 ` Demi Marie Obenour
2022-01-29 21:40 ` Zdenek Kabelac
2022-01-30 1:20 ` Demi Marie Obenour
2022-01-30 11:18 ` Zdenek Kabelac
2022-01-30 17:30 ` Demi Marie Obenour
2022-01-30 17:56 ` Zdenek Kabelac
2022-01-30 18:01 ` Demi Marie Obenour
2022-01-30 18:42 ` Zdenek Kabelac
2022-01-30 20:22 ` Gionatan Danti
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=YfgywUaJVsygv487@itl-email \
--to=demi@invisiblethingslab.com \
--cc=g.danti@assyoma.it \
--cc=linux-lvm@redhat.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 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.