The only people that have experienced it seem to be using cache tiering. I don't know if anyone has deeply investigate it yet. You could attempt to evict those objects from the cache tier so that the snapdir request is proxied down to the base tier to see if that works. On Fri, Jul 14, 2017 at 3:02 AM, 许雪寒 <xuxuehan@xxxxxx> wrote: > Yes, I believe so. Is there any workarounds? > > -----邮件原件----- > 发件人: Jason Dillaman [mailto:jdillama@xxxxxxxxxx] > 发送时间: 2017年7月13日 21:13 > 收件人: 许雪寒 > 抄送: ceph-users@xxxxxxxxxxxxxx > 主题: Re: 答复: No "snapset" attribute for clone object > > Quite possibly the same as this issue? [1] > > [1] http://tracker.ceph.com/issues/17445 > > On Thu, Jul 13, 2017 at 8:13 AM, 许雪寒 <xuxuehan@xxxxxx> wrote: >> By the way, we are using hammer version's rbd command to export-diff rbd images on Jewel version's cluster. >> >> -----邮件原件----- >> 发件人: ceph-users [mailto:ceph-users-bounces@xxxxxxxxxxxxxx] 代表 许雪寒 >> 发送时间: 2017年7月13日 19:54 >> 收件人: ceph-users@xxxxxxxxxxxxxx >> 主题: No "snapset" attribute for clone object >> >> We are using rbd for block devices of VMs, and recently we found that after we created snapshots for some rbd images, there existed such objects for which there are clone objects who doesn't have "snapset" extensive attributes with them. >> >> It seems that the lack of "snapset" attributes for clone objects has led to segmentation faults when we try to do "export-diff". >> >> Is this a bug? >> We are using 10.2.5, jewel version. >> >> Thank you:-) >> >> _______________________________________________ >> ceph-users mailing list >> ceph-users@xxxxxxxxxxxxxx >> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com >> _______________________________________________ >> ceph-users mailing list >> ceph-users@xxxxxxxxxxxxxx >> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com > > > > -- > Jason -- Jason _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com