Hi. I've asked this question years ago (in 2013): https://lists.openvz.org/pipermail/users/2013-August/005250.html
Let me know if it helps, but this bug should have been fixed in CentOS and RHEL at least: https://bugs.centos.org/view.php?id=6548 Maybe OpenVZ maintainers didn't pick up this fix in the openvz6 legacy kernel? Thanks. ср, 10 апр. 2019 г. в 10:45, Narcis Garcia <informat...@actiu.net>: > Does anybody know how can I solve this? > > $ lsb_release -d > Description: Devuan GNU/Linux 1.0 (jessie) > > $ uname -a > Linux bell1 2.6.32-openvz-042stab134.8-amd64 #1 SMP Fri Dec 7 17:18:40 > MSK 2018 x86_64 GNU/Linux > > $ lsblk --discard /dev/sda > NAME DISC-ALN DISC-GRAN DISC-MAX DISC-ZERO > sda 0 512B 2G 0 > ├─sda1 0 512B 2G 0 > └─sda2 0 512B 2G 0 > └─sda2_crypt 0 0B 0B 0 > > $ cat /etc/crypttab > sda2_crypt UUID=***** none luks,discard > > $ mount | grep -e discard > /dev/mapper/sda2_crypt on / type ext4 > (rw,noatime,errors=remount-ro,barrier=1,data=ordered,discard) > /dev/sda1 on /boot type ext4 (rw,relatime,barrier=1,data=ordered,discard) > > $ sudo fstrim / > fstrim: /: the discard operation is not supported > > Thank you. > > > _______________________________________________ > Users mailing list > Users@openvz.org > https://lists.openvz.org/mailman/listinfo/users >
_______________________________________________ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users