I am setting up a storage cluster on Ambedded ARM hardware, which is nice! I find that I can set up an erasure coded pool with the default k=2,m=1
The cluster has 9x OSD with HDD and 12xOSD with SSD If I configure another erasure profile such as k=7 m=2 then the pool creates, but the pgs stick in configuring/incomplete. Some advice please: a) what erasure profiles do people suggest for this setup b) a pool with m=1 will work fine of course, I imagine though a failed OSD has to be replaced quickly If anyone else has Ambedded, what crush rule do you select for the metadata when creating a pool?
_______________________________________________ ceph-users mailing list ceph-users@lists.ceph.com http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
