Dear Ceph Users,
I need your help to redesign my ceph storage network. As suggested in earlier discussions, i must not use SAN storage. So we have decided to removed it. Now we are ordering Local HDDs. My Network would be Host1 --> Controller + Compute1 Host 2--> Compute2 Host 3 --> Compute3 Is it right setup for ceph network? For Host1 and Host2 , we are using 1 500GB disk for OS on each host . Should we use same size storage disks 500GB *8 for ceph environment or i can order Disks in size of 2TB for ceph cluster? Making it 2T X 2 on Host1 2T X 2 on Host 2 2T X 2 on Host 3 12TB in total. replication factor 2 should make it 6 TB? Regards On Tue, Aug 2, 2016 at 11:16 AM, Gaurav Goyal <[email protected]> wrote: > > Hello Jason/Kees, > > I am trying to take snapshot of my instance. > > Image was stuck up in Queued state and instance is stuck up in Image > Pending Upload state. > > I had to manually quit the job as it was not working since last 1 hour .. > my instance is still in Image Pending Upload state. > > Is it something wrong with my ceph configuration? > can i take snapshots with ceph storage? How? > > Regards > Gaurav Goyal > > On Wed, Jul 13, 2016 at 9:44 AM, Jason Dillaman <[email protected]> > wrote: > >> The RAW file will appear to be the exact image size but the filesystem >> will know about the holes in the image and it will be sparsely >> allocated on disk. For example: >> >> # dd if=/dev/zero of=sparse-file bs=1 count=1 seek=2GiB >> # ll sparse-file >> -rw-rw-r--. 1 jdillaman jdillaman 2147483649 Jul 13 09:20 sparse-file >> # du -sh sparse-file >> 4.0K sparse-file >> >> Now, running qemu-img to copy the image into the backing RBD pool: >> >> # qemu-img convert -f raw -O raw ~/sparse-file rbd:rbd/sparse-file >> # rbd disk-usage sparse-file >> NAME PROVISIONED USED >> sparse-file 2048M 0 >> >> >> On Wed, Jul 13, 2016 at 3:31 AM, Fran Barrera <[email protected]> >> wrote: >> > Yes, but is the same problem isn't? The image will be too large because >> the >> > format is raw. >> > >> > Thanks. >> > >> > 2016-07-13 9:24 GMT+02:00 Kees Meijs <[email protected]>: >> >> >> >> Hi Fran, >> >> >> >> Fortunately, qemu-img(1) is able to directly utilise RBD (supporting >> >> sparse block devices)! >> >> >> >> Please refer to http://docs.ceph.com/docs/hammer/rbd/qemu-rbd/ for >> >> examples. >> >> >> >> Cheers, >> >> Kees >> >> >> >> On 13-07-16 09:18, Fran Barrera wrote: >> >> > Can you explain how you do this procedure? I have the same problem >> >> > with the large images and snapshots. >> >> > >> >> > This is what I do: >> >> > >> >> > # qemu-img convert -f qcow2 -O raw image.qcow2 image.img >> >> > # openstack image create image.img >> >> > >> >> > But the image.img is too large. >> >> >> >> _______________________________________________ >> >> ceph-users mailing list >> >> [email protected] >> >> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com >> > >> > >> > >> > _______________________________________________ >> > ceph-users mailing list >> > [email protected] >> > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com >> > >> >> >> >> -- >> Jason >> _______________________________________________ >> ceph-users mailing list >> [email protected] >> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com >> > >
_______________________________________________ ceph-users mailing list [email protected] http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
