> Op 17 oktober 2017 om 19:38 schreef Jason Dillaman <jdillama@xxxxxxxxxx>: > > > There is no existing option to thick provision images within RBD. When > an image is created or cloned, the only actions that occur are some > small metadata updates to describe the image. This allows image > creation to be a quick, constant time operation regardless of the > image size. To thick provision the entire image would require writing > data to the entire image and ensuring discard support is disabled to > prevent the OS from releasing space back (and thus re-sparsifying the > image). > Indeed. It makes me wonder why anybody would want it. It will: - Impact recovery performance - Impact scrubbing performance - Utilize more space then needed Why would you want to do this Sinan? Wido > On Mon, Oct 16, 2017 at 10:49 AM, <sinan@xxxxxxxx> wrote: > > Hi, > > > > I have deployed a Ceph cluster (Jewel). By default all block devices that > > are created are thin provisioned. > > > > Is it possible to change this setting? I would like to have that all > > created block devices are thick provisioned. > > > > In front of the Ceph cluster, I am running Openstack. > > > > Thanks! > > > > Sinan > > > > _______________________________________________ > > ceph-users mailing list > > ceph-users@xxxxxxxxxxxxxx > > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com > > > > -- > Jason > _______________________________________________ > 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
 |