Re: Editing Crush Map to fix osd_crush_chooseleaf_type = 0

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

 



My replica size on the pool is 3, so I'll use that to test. There is no other type in my map like dc, rack, etc; just servers. Do you know what a successful run of the test command looks like? I just ran it myself and it spits out a number of crush rules (in this case 1024) and then ends with: 

double free or corruption (out)
*** Caught signal (Aborted) **
 in thread 7f4915c58dc0 thread_name:crushtool

The show-bad-mappings version shows nothing and then spits out the same output as above. I'm going to assume that means it's working properly?
_______________________________________________
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