Re: [ceph-users] min_size vs. K in erasure coded pools

2019-02-21 Thread Paul Emmerich
You can reduce min_size to k in an ec pool. But that's a very bad idea for the same reason that min_size 1 on a replicated pool is bad. Paul -- Paul Emmerich Looking for help with your Ceph cluster? Contact us at https://croit.io croit GmbH Freseniusstr. 31h 81247 München www.croit.io Tel: +49

Re: [ceph-users] min_size vs. K in erasure coded pools

2019-02-20 Thread Eugen Block
Hi, I see that as a security feature ;-) You can prevent data loss if k chunks are intact, but you don't want to work with the least required amount of chunks. In a disaster scenario you can reduce min_size to k temporarily, but the main goal should always be to get the OSDs back up. For ex

[ceph-users] min_size vs. K in erasure coded pools

2019-02-20 Thread Clausen , Jörn
Hi! While trying to understand erasure coded pools, I would have expected that "min_size" of a pool is equal to the "K" parameter. But it turns out, that it is always K+1. Isn't the description of erasure coding misleading then? In a K+M setup, I would expect to be good (in the sense of "no