| Hi Ilya,
It could really improve BLOCK performance for oracle / database workload
Thanks for your feedback
On Sat, Dec 27, 2014 at 6:46 PM, Florent MONTHEL < fmonthel@xxxxxxxxxxxxx> wrote: Hi,
I’ve just created image with striping support like below (image type 2 - 16
stripes of 64K with 4MB object) :
rbd create sandevices/flaprdweb01_lun010 --size 102400 --stripe-unit 65536
--stripe-count 16 --order 22 --image-format 2
rbd info sandevices/flaprdweb01_lun010
rbd image 'flaprdweb01_lun010':
size 102400 MB in 25600 objects
order 22 (4096 kB objects)
block_name_prefix: rbd_data.40c52ae8944a
format: 2
features: layering, striping
stripe unit: 65536 bytes
stripe count: 16
But when I try to map device, I’ve unsupported striping alert on my dmesg
console.
rbd map sandevices/flaprdweb01_lun010 --name client.admin
rbd: sysfs write failed
rbd: map failed: (22) Invalid argument
dmesg | tail
[15352.510385] rbd: image flaprdweb01_lun010: unsupported stripe unit (got
65536 want 4194304)
Do you know if it’s scheduled to support STRIPINGV2 on tbd client ?
How can I mount my device ?
You can't - krbd doesn't support it yet. It's planned, in fact it's the top item on the krbd list. Currently STRIPINGV2 images can be mapped only if su=4M and sc=1 (i.e. if striping params match v1 images) and that's the error you are tripping over. Thanks, Ilya
|
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
