Hi Alwin, On 7/10/24 15:55, Alwin Antreich wrote:

Hi Dietmar,

On Wed, 10 Jul 2024 at 11:22, Dietmar Rieder <dietmar.rieder@i-med.ac.at <mailto:dietmar.rieder@i-med.ac.at>> wrote:

Hi,

Am 9. Juli 2024 13:37:58 MESZ schrieb Dietmar Rieder <dietmar.rieder@i-med.ac.at <mailto:dietmar.rieder@i-med.ac.at>>: >Hi, > >we noticed the following ceph errors in the kernel messages (dmesg -T): > >[Tue Jul  9 11:59:24 2024] ceph: ceph_fill_inode 10003683698.fffffffffffffffe BAD symlink size 0 > >Is this something that we should be worried about? > >We are currently trying to identify the inode/file using: > ># find /data -inum 10003683698 -printf "%i %p\n" > >Could deleting the inode fix the issue? If not what can we do?

find did not return anything. The error keeps showing up , has someone an idea?

Not really but looking at the kernel code where I found the error message, the comment suggests (ceph_fill_inode) that it could also be a new inode. https://github.com/torvalds/linux/blob/v6.9/fs/ceph/inode.c#L1197 <https://github.com/torvalds/linux/blob/v6.9/fs/ceph/inode.c#L1197>

thanks, we have found that kernel client code as well but could not find a root cause of the error due to lacking insights. Anyway, we were now able to identify the symlink and was working as expected, i.e. it could be listed and the target file could be read via the symlink. We now deleted it and we will keep an eye on these messages. Cheers Dietmar