On Sat, 6 Oct 2018, Vasiliy Tolstov wrote: > сб, 6 окт. 2018 г. в 0:07, Vasiliy Tolstov <v.tolstov@xxxxxxxxx>: > > > > сб, 6 окт. 2018 г. в 0:05, Vasiliy Tolstov <v.tolstov@xxxxxxxxx>: > > > > > > > > > crushtool -c map.txt -o map.bin not creates map.bin file. > > > > > > > Never mind, i fix text crush map and now crushtool compiles fine > > > > Now i'm able to decode crushmap buckets, and rules. Format not very > hard. All data as i understand in LittleEndian. > Now i'm at this : > // name info > // NOTE: we had a bug where we were incoding int instead of int32, > which means the > // 'key' field for these maps may be either 32 or 64 bits, depending. tolerate > // both by assuming the string is always non-empty. > > Does this bug present in latest ceph release or not? What you think > about feature encoding int32 or int64? It's int32_t, now. This was fixed before bobtail, back in 2012, so we could probably even remove this compat code. sage
