My radosgw-admin orphans find generated +64 shards and it show a lot of 
_shadow_ , _multipart and other undefined object type.

 

Waiting for someone clarify what to do with the output.

 

Regards

 

De: P. O. <pos...@gmail.com> 
Enviado el: martes, 24 de septiembre de 2019 11:26
Para: ceph-users@ceph.io
Asunto: [ceph-users] RGW orphaned shadow objects

 

Hi All,

I have a question about "orphaned" objects in default.rgw.buckets.data pool.
Few days ago i ran "radosgw-admin orphans find ..."

[dc-1 root@mon-1 tmp]$ radosgw-admin orphans list-jobs
[
    "orphans-find-1"
]

Today I checked the result. I listed orphaned objects by command:

$# for i in `rados -p default.rgw.log ls |grep 
orphan.scan.orphans-find-1.rados`; do rados -p default.rgw.log listomapkeys $i; 
done > orphaned_objects.txt

There are a lot: xxx.__shadow_.yyy objects.

Is it possible to check if these __shadow_ are orphaned (can be removed) or 
belongs to any good object?
How to check if a shadow object is still in use and what object it belongs to?

 

Some of them are very old.

 

For example: 

default.rgw.buckets.data/23a033d8-1146-2345-9f94-81383220c334.3130618.2__shadow_.-GOuvdWROljudUgTgq6u6wRR-lHoxU0_1
 mtime 2017-08-16 04:01:49.000000, size 4194304
default.rgw.buckets.data/23a033d8-1146-2345-9f94-81383220c334.3130618.2__shadow_.-GOuvdWROljudUgTgq6u6wRR-lHoxU0_2
 mtime 2017-08-16 04:01:49.000000, size 4194304
default.rgw.buckets.data/23a033d8-1146-2345-9f94-81383220c334.3130618.2__shadow_.-GOuvdWROljudUgTgq6u6wRR-lHoxU0_4
 mtime 2017-08-16 04:01:49.000000, size 4194304
default.rgw.buckets.data/23a033d8-1146-2345-9f94-81383220c334.3130618.2__shadow_.-GOuvdWROljudUgTgq6u6wRR-lHoxU0_5
 mtime 2017-08-16 04:01:49.000000, size 4194304
default.rgw.buckets.data/23a033d8-1146-2345-9f94-81383220c334.3130618.2__shadow_.-GOuvdWROljudUgTgq6u6wRR-lHoxU0_6
 mtime 2017-08-16 04:01:49.000000, size 4194304

 

Best regards,
PO

_______________________________________________
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io

Reply via email to