resize2fs is some kind of incremental, I guess You may notice that on a slow system, if you give many more spaces to a large partition Running resize2fs on a screen, and watching df -h on an other will show you an incremental increase of disk space Maybe the discard option can help you on that case, if it's really an issue, and if your software support it man ext4 said: >discard/nodiscard > Controls whether ext4 should issue discard/TRIM commands to the > underlying block device when blocks are freed. This is useful > for SSD devices and sparse/thinly-provisioned LUNs, but it is > off by default until sufficient testing has been done. On 16/06/2016 12:24, Zhongyan Gu wrote: > Hi, > it seems using resize2fs on rbd image would generate lots of garbage > objects in ceph. > The experiment is: > 1. use resize2fs to extent 50G rbd image A to 400G image with ext4 format > in vm. > 2. calculate the total object size in rbd pool, 35GB(already divided by > replicas#). > 3. cone ImageB based on 400G image A. then flatten Image B. > 4. after flatten, calculate the total object size in rbd pool and Image B's > actual size is 14GB. > > I'm confused why Image B size is 14GB, not the same as Image A. > The only possible way that can explain that is resize2fs generate a lot of > garbage objects in rbd. And flatten ignored those garbage files. > Anyone can help me confirm this?? > > > thanks > Cory > > > > _______________________________________________ > ceph-users mailing list > ceph-users@xxxxxxxxxxxxxx > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com > _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |