Hi,
Some of our Proxmox VE users have noticed that a large fstrim inside a
QEMU/KVM guest does not free up as much space as expected on the backing
RBD image -- if the image is mapped on the host via KRBD and passed to
QEMU as a block device (checked via `rbd du --exact`). If the image is
attached
Hi Ilya,
Thank you for your illuminating response!
I thought I had checked `ceph df` during my experiments before, but
apparently not carefully enough. :)
On 25/10/2024 18:43, Ilya Dryomov wrote:
> "rbd du" can be very imprecise even with --exact flag: one can
> construct an image that would use
Hi Ilya,
some of our Proxmox VE users also report they need to enable rxbounce to
avoid their Windows VMs triggering these errors, see e.g. [1]. With
rxbounce, everything seems to work smoothly, so thanks for adding this
option. :)
We're currently checking how our stack could handle this more
gra
Hi Ilya,
On 13/12/2024 16:25, Ilya Dryomov wrote:
> [...]
>> We're currently checking how our stack could handle this more
>> gracefully. From my understanding of the rxbounce option, it seems like
>> always passing it when mapping a volume (i.e., even if the VM disks
>> belong to Linux VMs that a
