Well, Am 21.05.2013 um 21:31 schrieb Sage Weil <sage@xxxxxxxxxxx>: > On Tue, 21 May 2013, Stefan Priebe wrote: >> Am 21.05.2013 17:44, schrieb Sage Weil: >>> On Tue, 21 May 2013, Stefan Priebe - Profihost AG wrote: >>>> Am 21.05.2013 um 17:35 schrieb Sylvain Munaut >>>> <s.munaut@xxxxxxxxxxxxxxxxxxxx>: >>>> >>>>> Hi, >>>>> >>>>>> subject seems familiar, version was 0.48.3 in the last mail. >>>>>> >>>>>> Not anyone else with perhaps large pg's experiencing such behaviour? >>>>>> >>>>>> Any advice on how to proceed? >>>>> >>>>> I had the same behavior in both argonaut and bobtail, raising sharply >>>>> ~ 100M or so at each scrub (every 24h). >>>>> >>>>> It's now resolved in cuttlefish AFAICT. >>>>> >>>>> However given the mon leveldb issues I'm having with cuttlefish, I'm >>>>> not sure I'd recommend upgrading ... >>>> >>>> I thought all mon leveldb issues were solved? >>> >>> Not quite. I'm now able to reproduce the leveldb growth from Mike >>> Dawson's trace (thanks!) but we don't have a fix yet. >> >> Oh OK. Is there a tracker id? > > http://tracker.ceph.com/issues/4895 > true for this issue, but back to topic, still not being able to safely ( deep-) scrub the whole cluster with 0.56.6. >> >>> I thought the scrub memory issues were addressed by >>> f80f64cf024bd7519d5a1fb2a5698db97a003ce8 in 0.56.4... :( >>> any advice very welcome, though about 1/3 of the cluster is safe in means of "we scrubbed it deeply". Best regards, Oliver. >>> sage >>> >> >> > -- > To unsubscribe from this list: send the line "unsubscribe ceph-devel" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
