Re: mds damage cannot repair

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



A "backtrace" is an xattr on the RADOS object storing data for a given
file, and it contains the file's (versioned) path from the root. So a
bad backtrace means there's something wrong with that — possibly just
that there's a bug in the version of the code that's checking it,
because they're generally out of date and that's okay; it's definitely
not critical because they're only used for disaster recovery or in
some rare ino-based lookup cases if there's a hard link to the file or
some rare nfs situations.

The "bad remote dentry" message means that you had a link and...I
don't actually remember the details of this one.

But my guess is that the relevant files were just auto-deleted and not
critical to the software anyway, so that's why the error went away.
Incorrect handling of them being checked while being deleted them
might also be why a warning was spawned to begin with.
-Greg

On Mon, Feb 13, 2023 at 5:43 AM Andrej Filipcic <andrej.filipcic@xxxxxx> wrote:
>
> On 2/10/23 08:50, Andrej Filipcic wrote:
>
> FYI, the damage went away after a couple of days, not quite sure how.
>
> Best,
> Andrej
>
> >
> > Hi,
> >
> > there is mds damage on our cluster, version 17.2.5,
> >
> > [
> >    {
> >        "damage_type": "backtrace",
> >        "id": 2287166658,
> >        "ino": 3298564401782,
> >        "path": "/hpc/home/euliz/.Xauthority"
> >    }
> > ]
> >
> >
> >
> > The recursive repair does not fix it,
> > ...ceph tell mds.0 scrub start /hpc/home/euliz force,repair,recursive
> >
> > mds log:
> >
> > 2023-02-10T07:01:34.012+0100 7f46df3ea700  0 mds.0.cache  failed to
> > open ino 0x30001c26a76 err -116/0
> > 2023-02-10T07:01:34.012+0100 7f46df3ea700  0 mds.0.cache
> > open_remote_dentry_finish bad remote dentry [dentry
> > #0x1/hpc/home/euliz/.Xauthority [568,head] auth
> > REMOTE(reg) (dversion lock) pv=0 v=4425667830 ino=(nil)
> > state=1073741824 | ptrwaiter=1 0x5560eb33a780]
> >
> >
> > Any clue how to fix this? or remove the file from namespace? it is not
> > important...
> >
> > Thanks,
> > Andrej
> >
> > --
> > _____________________________________________________________
> >     prof. dr. Andrej Filipcic,   E-mail:Andrej.Filipcic@xxxxxx
> >     Department of Experimental High Energy Physics - F9
> >     Jozef Stefan Institute, Jamova 39, P.o.Box 3000
> >     SI-1001 Ljubljana, Slovenia
> >     Tel.: +386-1-477-3674    Fax: +386-1-477-3166
> > -------------------------------------------------------------
>
>
> --
> _____________________________________________________________
>     prof. dr. Andrej Filipcic,   E-mail:Andrej.Filipcic@xxxxxx
>     Department of Experimental High Energy Physics - F9
>     Jozef Stefan Institute, Jamova 39, P.o.Box 3000
>     SI-1001 Ljubljana, Slovenia
>     Tel.: +386-1-477-3674    Fax: +386-1-477-3166
> -------------------------------------------------------------
> _______________________________________________
> ceph-users mailing list -- ceph-users@xxxxxxx
> To unsubscribe send an email to ceph-users-leave@xxxxxxx
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx




[Index of Archives]     [Information on CEPH]     [Linux Filesystem Development]     [Ceph Development]     [Ceph Large]     [Ceph Dev]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux