Hello,

New cluster, Jewel, setting up cache-tiering:
---
Error EPERM: 'readforward' is not a well-supported cache mode and may corrupt 
your data.  pass --yes-i-really-mean-it to force.
---

That's new and certainly wasn't there in Hammer, nor did it whine about
this when upgrading my test cluster to Jewel.

And speaking of whining, I did that about this and readproxy, but not
their stability (readforward has been working nearly a year flawlessly in
the test cluster) but their lack of documentation.

So while of course there is no warranty for anything with OSS, is there
any real reason for the above scaremongering or is that based solely on
lack of testing/experience?

Christian
-- 
Christian Balzer        Network/Systems Engineer                
ch...@gol.com           Rakuten Communications
_______________________________________________
ceph-users mailing list
ceph-users@lists.ceph.com
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com

Reply via email to