Skip to content
Discussion options

You must be logged in to vote

@bruce20319 Hey, this is not a lotus bug. It seems like a simple kernel panic on truncate option. So, while lotus was deleting the cache file, it requested the OS to do so. The part of this delete operation is to remove the inode corresponding to that file. The inode truncate API for the kernel is where the panic occurred. If this is a one time thing, then I would suggest to ignore it. But if it is reproducible then you should file a bug with Linux kernel.

Replies: 2 comments 1 reply

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
1 reply
@LexLuthr
Comment options

Answer selected by LexLuthr
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/sealing status/archived Archive label, use when closing/locking old discussions.
3 participants
Converted from issue

This discussion was converted from issue #7988 on January 23, 2022 00:17.