Worst case I’ve seen was fsck after unclean shutdown taking ~15 hours to process a 20TB drive almost filled with Storj pieces. How much RAM does your fsck process take?
Fun fact is, that it is still running. 73 days now.
Does it ever work? Because it sounds like a too much time for the not so big volume.
I really don’t know what this thing is doing.
It seems like it is checking every single inode from 0 to 100 Mill or whatever and attaches it to lost and found.
Bloody hell, after a month of it running you kinda just keep it going out of a sheer sense of morbid curiosity…
Yes, I should stop it but at the same time I am wondering if this will ever end how long it will take.
1 Like
Is there actually any I/O going on? Sounds like the thing may have stalled…
Yes, it has not stalled.
It is basically this: https://www.linuxquestions.org/questions/linux-server-73/please-help-smart-dd-fsck-millions-of-unattached-inodes-4175521810/
-It looks like its going thru millions of those innodes.
And as it looks like that error with inode number is increasing by 1,
Inode 7216654 ref count is 2, should be1.
and next
Inode 7216655 ref count is 2, should be1.
So that inode number is increasing by 1 , so basically every inode.
The count goes up steadily…
Let us know when it’s finished
I feel like I should send you a beer to celebrate 
2 Likes