On Fri, Mar 13, 2020 at 11:36 AM Matt Dunavant <mdunav...@convokesystems.com> wrote: > > Jason Dillaman wrote: > > On Fri, Mar 13, 2020 at 11:17 AM Matt Dunavant > > <mdunavant(a)convokesystems.com> wrote: > > > > > > I'm not sure of the last known good release of the rbd CLI where this > > > worked. I just > > > ran the sha1sum against the images and they always come up as different. > > > Might be worth > > > knowing, this is a volume that's provisioned at 512GB (with much less > > > actually used) > > > but after export, it only shows up as about 56GB. > > The resulting image from the "rbd import" only shows up as 56GiB? > > > > > _______________________________________________ > > > ceph-users mailing list -- ceph-users(a)ceph.io > > > To unsubscribe send an email to ceph-users-leave(a)ceph.io > > > > Yeah, it's super odd. The actual content in the 512GB rbd image is probably > about 50ish GB but the command isn't killing itself early or throwing any > errors. I believe when I run the export to a middleman and then import, the > image shows up as the correct size. I'll test that in a bit.
Couple test cases to try: Does the "rbd export" progress bar get to 100%? If you run "rbd export - > some_file" does it create a 512GiB file? If you run "rbd import" with a "--sparse-size 0" argument, does it change the result? > _______________________________________________ > ceph-users mailing list -- ceph-users@ceph.io > To unsubscribe send an email to ceph-users-le...@ceph.io > -- Jason _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-le...@ceph.io
