Re: RBD image copying

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Le 14/05/2013 13:00, Wolfgang Hennerbichler a écrit :

On 05/14/2013 12:16 PM, Greg wrote:
...
And try to mount :
root@client2:~# mount /dev/rbd1 /mnt/
root@client2:~# umount /mnt/
root@client2:~# mount /dev/rbd2 /mnt/
mount: you must specify the filesystem type
What strikes me is the copy is superfast and I'm in a pool in format 1
which, as far as I understand, is not supposed to support copy-on-write.

I tried listing the pool (with rados tool) and it show the p2b16.rbd
file is there but no rb.0.X.Y.offset is present for p2b16 (name can be
found from p2b16.rbd), while there is for p1b16.

Did I not understand the copy mechanism ?
you sure did understand it the way it is supposed to be. something's
wrong here. what happens if you dd bs=1024 count=1 | hexdump your
devices, do you see differences there? is your cluster healthy?

Wolfgang,

after a copy, there is an "index" file (.rbd file) but no "data" file.

When I map the block device, I can read/write from/to it, when writing the "data" files are created and I can read them back.

Regards,
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com





[Index of Archives]     [Information on CEPH]     [Linux Filesystem Development]     [Ceph Development]     [Ceph Large]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux