General best practice for stripe unit and count if I want to change object size

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

 



This was asked in reddit and was requested to post here:

So in RBD, say I want to make an image that's got an object size of 1M instead of the default 4M (if it will be a VM say, and likely not have too many big files in it, just OS files mostly). I also know I don't wanna go too crazy and make 4k objects or the cluster will blow up with number of objects. What's a good rule of thumb on what to set the stripe unit and count in relation to object size?

Also how can I see the stripe unit and count for an image, it seems "rbd info <img-name>" doesn't show it, only object size (or order).



Would this be sensible (assuming old img is default 4M obj size) or really stupid and why?

rbd cp --object-size 1M --stripe-unit 1M --stripe-count 1 pool/old-img pool/new-img



I'm trying to get my head around striping and I tried using this page (https://docs.ceph.com/en/latest/dev/file-striping/) to understand what's going on low level, but it's just leaving me more confused the more I read it.
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx



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


  Powered by Linux