RBD thin provisioning and time to format a volume
Hello, My understanding is that the time to format an RBD volume is not dependent on its size as the RBD volumes are thin provisioned. Is this correct? For example, formatting a 1G volume should take almost the same time as formatting a 1TB volume - although accounting for differences in latencies due to load on the Ceph cluster. Is that a fair assumption? Thanks, Shridhar
On Wed, Jul 8, 2020 at 3:28 PM Void Star Nill <void.star.nill@gmail.com> wrote:
Hello,
My understanding is that the time to format an RBD volume is not dependent on its size as the RBD volumes are thin provisioned. Is this correct?
For example, formatting a 1G volume should take almost the same time as formatting a 1TB volume - although accounting for differences in latencies due to load on the Ceph cluster. Is that a fair assumption?
Yes, that is a fair comparison when creating the RBD image. However, a format operation might initialize and discard extents on the disk, so a larger disk will take longer to format.
Thanks, Shridhar _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io
-- Jason
On Wed, Jul 8, 2020 at 4:56 PM Jason Dillaman <jdillama@redhat.com> wrote:
On Wed, Jul 8, 2020 at 3:28 PM Void Star Nill <void.star.nill@gmail.com> wrote:
Hello,
My understanding is that the time to format an RBD volume is not
dependent
on its size as the RBD volumes are thin provisioned. Is this correct?
For example, formatting a 1G volume should take almost the same time as formatting a 1TB volume - although accounting for differences in latencies due to load on the Ceph cluster. Is that a fair assumption?
Yes, that is a fair comparison when creating the RBD image. However, a format operation might initialize and discard extents on the disk, so a larger disk will take longer to format.
Thanks for the response Jason. Could you please explain a bit more on the the format operation? Is there a relative time that we can determine based on the volume size? Thanks Shridhar
Thanks, Shridhar _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io
-- Jason
On Thu, Jul 9, 2020 at 12:02 AM Void Star Nill <void.star.nill@gmail.com> wrote:
On Wed, Jul 8, 2020 at 4:56 PM Jason Dillaman <jdillama@redhat.com> wrote:
On Wed, Jul 8, 2020 at 3:28 PM Void Star Nill <void.star.nill@gmail.com> wrote:
Hello,
My understanding is that the time to format an RBD volume is not dependent on its size as the RBD volumes are thin provisioned. Is this correct?
For example, formatting a 1G volume should take almost the same time as formatting a 1TB volume - although accounting for differences in latencies due to load on the Ceph cluster. Is that a fair assumption?
Yes, that is a fair comparison when creating the RBD image. However, a format operation might initialize and discard extents on the disk, so a larger disk will take longer to format.
Thanks for the response Jason. Could you please explain a bit more on the the format operation?
I'm not sure what else there is to explain. When you create a file system on top of any block device, it needs to initialize the block device. Depending on the file system, it might take more time for larger block devices because it's doing more work.
Is there a relative time that we can determine based on the volume size?
Thanks Shridhar
Thanks, Shridhar _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io
-- Jason
-- Jason
Thanks Jason. Do you mean to say some filesystems will initialize the entire disk during format? Does that mean we will see the entire size of the volume getting allocated during formatting? Or do you mean to say, some filesystem formatting just takes longer than others, as it does more initialization? I am just trying to understand if there are cases where Ceph will allocate all the blocks for a filesystem during formation operations, OR if they continue to be thin provisioned (allocate as you go based on real data). So far I have tried with ext3, ext4 and xfs and none of them dont allocate all the blocks during format. -Shridhar On Thu, 9 Jul 2020 at 06:58, Jason Dillaman <jdillama@redhat.com> wrote:
On Thu, Jul 9, 2020 at 12:02 AM Void Star Nill <void.star.nill@gmail.com> wrote:
On Wed, Jul 8, 2020 at 4:56 PM Jason Dillaman <jdillama@redhat.com>
On Wed, Jul 8, 2020 at 3:28 PM Void Star Nill <void.star.nill@gmail.com>
wrote:
Hello,
My understanding is that the time to format an RBD volume is not
dependent
on its size as the RBD volumes are thin provisioned. Is this correct?
For example, formatting a 1G volume should take almost the same time as formatting a 1TB volume - although accounting for differences in latencies due to load on the Ceph cluster. Is that a fair assumption?
Yes, that is a fair comparison when creating the RBD image. However, a format operation might initialize and discard extents on the disk, so a larger disk will take longer to format.
Thanks for the response Jason. Could you please explain a bit more on
wrote: the the format operation?
I'm not sure what else there is to explain. When you create a file system on top of any block device, it needs to initialize the block device. Depending on the file system, it might take more time for larger block devices because it's doing more work.
Is there a relative time that we can determine based on the volume size?
Thanks Shridhar
Thanks, Shridhar _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io
-- Jason
-- Jason
What about ntfs? You have there a not quick option. Maybe it writes to the whole disk some random pattern. Why do you ask? -----Original Message----- Cc: ceph-users Subject: [ceph-users] Re: RBD thin provisioning and time to format a volume Thanks Jason. Do you mean to say some filesystems will initialize the entire disk during format? Does that mean we will see the entire size of the volume getting allocated during formatting? Or do you mean to say, some filesystem formatting just takes longer than others, as it does more initialization? I am just trying to understand if there are cases where Ceph will allocate all the blocks for a filesystem during formation operations, OR if they continue to be thin provisioned (allocate as you go based on real data). So far I have tried with ext3, ext4 and xfs and none of them dont allocate all the blocks during format. -Shridhar On Thu, 9 Jul 2020 at 06:58, Jason Dillaman <jdillama@redhat.com> wrote:
On Thu, Jul 9, 2020 at 12:02 AM Void Star Nill <void.star.nill@gmail.com> wrote:
On Wed, Jul 8, 2020 at 4:56 PM Jason Dillaman <jdillama@redhat.com>
wrote:
On Wed, Jul 8, 2020 at 3:28 PM Void Star Nill <void.star.nill@gmail.com>
wrote:
Hello,
My understanding is that the time to format an RBD volume is not
dependent
on its size as the RBD volumes are thin provisioned. Is this correct?
For example, formatting a 1G volume should take almost the same time as formatting a 1TB volume - although accounting for differences in latencies due to load on the Ceph cluster. Is that a fair assumption?
Yes, that is a fair comparison when creating the RBD image. However, a format operation might initialize and discard extents on
the disk, so a larger disk will take longer to format.
Thanks for the response Jason. Could you please explain a bit more on the the format operation?
I'm not sure what else there is to explain. When you create a file system on top of any block device, it needs to initialize the block device. Depending on the file system, it might take more time for larger block devices because it's doing more work.
Is there a relative time that we can determine based on the volume size?
Thanks Shridhar
Thanks, Shridhar _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send
an email to ceph-users-leave@ceph.io
-- Jason
-- Jason
_______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io
participants (3)
-
Jason Dillaman
-
Marc Roos
-
Void Star Nill