Hi Eugen, in essence I would like the property "thick provisioned" to be sticky after creation and apply to any other operation that would be affected. To answer the use-case question: this is a disk image on a pool designed for predictable high-performance. On images on this pool we need to avoid any latency spikes due to on-demand allocation of non-provisioned objects. It is kind of strange that the rbd cli API is incomplete with regard to the thick provision property. I'm not sure if a flatten will have the desired effect. It just merges all snapshots, which does not require to allocate unallocated objects if they are not present in any snapshot. An un-sparsify image would do that. Did anyone find a reasonable work-around except maybe a dd after the end of the existing objects? Or a dd of the disk image onto itself? Best regards, ================= Frank Schilder AIT Risø Campus Bygning 109, rum S14 ________________________________________ From: Eugen Block <eblock@xxxxxx> Sent: 15 June 2022 14:54:54 To: ceph-users@xxxxxxx Subject: Re: rbd resize thick provisioned image So basically, you need the reverse sparsify command, right? ;-) I only find several mailing list thready asking why someone would want thick-provisioning but it happened eventually. I suppose cloning and flattening the resulting image is not a desirable workaround. Zitat von Frank Schilder <frans@xxxxxx>: > Hi all, > > I need to increase the size of images created with > --thick-provision. Using resize will just change the provisioned > size, but not allocate/initialize the additional space. I seem to be > unable to find an option that will maintain thick provisioning of an > image when resizing. > > Is there a way to resize thick provisioned images properly, that is, > maintaining thick provisioning? > > Thanks and best regards, > ================= > Frank Schilder > AIT Risø Campus > Bygning 109, rum S14 > _______________________________________________ > ceph-users mailing list -- ceph-users@xxxxxxx > To unsubscribe send an email to ceph-users-leave@xxxxxxx _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
 |