Hi Frank,
On 7/31/2020 10:31 AM, Frank Schilder wrote:
Hi Igor,
thanks. I guess the problem with finding the corresponding images is, that it
happens on bluestore and not on object level. Even if I listed all rados
objects and added their sizes I would not see the excess storage.
Thinking ab
>> Full disclosure: I have no relationship with Linode except as a
customer.
So why mention them? I have often abuse coming from linode. So I rather
see that linode has 0 clients.
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send
I can understand the benefits of having a CO, I am still testing with
mesos. However what is the benefit of having ceph daemons running in CO
environment? Except for your mds, mrg and radosgw, your osd daemons are
bound to the hardware / disks they are running on. It is not like if
osd.121 g
Hi,
In *mapper.c* file of Ceph CRUSH, I am trying to understand the definition
of a linux macro ```*S64_MIN*``` used in the following ```*else*```
condition i.e. ```*draw = S64_MIN*```.
Which exact decimal value is meant here for ```*S64_MIN*```?
```
if (weights[i])
{
u = hash(buck
On Sat, Aug 1, 2020 at 5:50 AM Marc Roos wrote:
> I can understand the benefits of having a CO, I am still testing with
> mesos. However what is the benefit of having ceph daemons running in CO
> environment?
As I said in my original post, I use this for testing CephFS.
There's no reason why you
Hi List,
We see newly added OSD take long time to become active, it is
fetching old osdmaps from monitors. Curious why it need that much
historical ? The cluster is stable , no osd down/out except the ongoing
cap add (one osd at a time).
{
"cluster_fsid": "e959f744-64be-4f4e-9606-103c
