Hi Paul,
thanks for the hint.
I did a recursive scrub from "/". The log says there where some inodes with bad
backtraces repaired. But the error remains.
May this have something to do with a deleted file? Or a file within a snapshot?
The path told by
# ceph tell mds.mds3 damage ls
2019-08-19 13:43:04.608 7f563f7f6700 0 client.894552 ms_handle_reset on
v2:192.168.16.23:6800/176704036
2019-08-19 13:43:04.624 7f56407f8700 0 client.894558 ms_handle_reset on
v2:192.168.16.23:6800/176704036
[
{
"damage_type": "backtrace",
"id": 3760765989,
"ino": 1099518115802,
"path": "~mds0/stray7/100005161f7/dovecot.index.backup"
}
]
starts a bit strange to me.
Are the snapshots also repaired with a recursive repair operation?
Thanks
Lars
Mon, 19 Aug 2019 13:30:53 +0200
Paul Emmerich <paul.emmer...@croit.io> ==> Lars Täuber <taeu...@bbaw.de> :
> Hi,
>
> that error just says that the path is wrong. I unfortunately don't
> know the correct way to instruct it to scrub a stray path off the top
> of my head; you can always run a recursive scrub on / to go over
> everything, though
>
>
> Paul
>
--
Informationstechnologie
Berlin-Brandenburgische Akademie der Wissenschaften
Jägerstraße 22-23 10117 Berlin
Tel.: +49 30 20370-352 http://www.bbaw.de
_______________________________________________
ceph-users mailing list
ceph-users@lists.ceph.com
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
