* discard on snapshot-origin target
@ 2016-05-20 15:08 Marek Marczykowski-Górecki
0 siblings, 0 replies; only message in thread
From: Marek Marczykowski-Górecki @ 2016-05-20 15:08 UTC (permalink / raw)
To: dm-devel
[-- Attachment #1.1: Type: text/plain, Size: 790 bytes --]
Hi,
Is it possible to enable DISCARD support for snapshot-origin target?
Currently it returns EOPNOTSUPP even if underlying device does support
it. I know there are some cases when it isn't desirable (for example
mkfs.ext4 discards the entire device, which would trigger copyout to the
snapshot), but I can live with that.
Or, if possible, better to prevent that copyout if discarded block(s)
were zeroed already. Which would handle the case of mkfs.ext4 on empty,
zeroed device.
I see that it may undesired in some cases, so maybe some configurable
option? Like module parameter or so?
--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2016-05-20 15:08 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-05-20 15:08 discard on snapshot-origin target Marek Marczykowski-Górecki
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.