Displaying 3 results from an estimated 3 matches for "pool00".
Did you mean:
pool0
2016 Jan 20
1
LVM thin volumes fstrim operation not supported
...im reports that it worked but the
LVs Data% does not decrease after the fstrim. xfs just throws the
error.
I've also been looking at the output of lsblk -D
# lsblk -D
NAME DISC-ALN DISC-GRAN DISC-MAX DISC-ZERO
xvdb 0 0B 0B 0
??data-pool00_tmeta 0 0B 0B 0
? ??data-pool00-tpool 0 0B 0B 0
? ??data-pool00 0 0B 0B 0
? ??data-data 0 0B 0B 0
??data-pool00_tdata 0 0B 0B 0
??data-pool...
2016 Jan 19
2
LVM thin volumes fstrim operation not supported
Hi All
I'm trying to setup my LVM thin pool to support discards so that the pool
can reclaim space even if the underlying device doesn't support trim. It is
my understanding that all thin pools should support trim even if the
underlying device doesn't. (please correct me if I'm wrong here)
I have one centos server that does support trim and everything is working
correctly but any
2014 Jul 22
0
CentOS7+kickstart+thinpool = error/exception
...using this option and this is the anaconda file produced:
part /boot --fstype="xfs" --ondisk=vda --size=500
part pv.10 --fstype="lvmpv" --ondisk=vda --size=7691
volgroup centos_centos7 --pesize=4096 pv.10
logvol --fstype="None" --grow --size=1232 --thinpool --name=pool00
--vgname=centos_centos7
logvol swap --fstype="swap" --size=819 --name=swap --vgname=centos_centos7
logvol / --fstype="xfs" --grow --maxsize=51200 --size=1024 --thin
--poolname=pool00 --name=root --vgname=centos_centos7
The Problem is that when I use this as the basis for a ki...