19.06.2023 14:14, Chris Hofstaedtler wrote:
I'm not sure what you're asking. Is this a bug? A feature request?
blkdiscard is a "low level tool" and I think it works according to
its documentation. A less low-level tool is fstrim, that might do
what you want?
If you want blkdiscard to be smarter - if the smartness shouldn't be
in the kernel in the first place - can you suggest this to upstream?
Doesn't seem like this is a Debian-specific thing?
It definitely is not debian-specific, this is why I tagged it "upstream"
to begin with.
Note that `lsblk' utility also belongs to the same util-linux package,
and this utility knows how to find the max unmap size, so it's just a
missing call to already existing functionality.
Yes, blkdiscard works according to the docs, but since it is used in
particular scenarios, I'd say it is a bug on its part.
Why I'm filing it with debian: because it needs to be documented at
the very least. Usually when someone bug one of the software I
maintain in debian, I can know better how to contact upstream on
behalf of this reporter, or when a problem is complex or too
specific to particular user's setup so I can't reproduce it, I
suggest them to ask upstream directly. It is about knowing packages
you maintain. In recent years I had to register in just too many
places and subscribe to too many mailing lists just to be able to
report issues/bugs. I tend to avoid doing so unless really
necessary. If you don't have util-linux upstream contacts, I
can register/subscribe there for sure...
Thanks,
/mjt
