fsck finds illegal block(s) in one inode
Then it tells there are too many illegal blocks in inode and asks
Clear indoe? yes
Then it restarts and... asks at the same place about illegal blocks. It clears the next 11 and tells there are too many. And so on.
With debugfs I tried manually to clear this inode. It tells also there are invalid blocks, and these remain in inode. clri clears the indoe but after close and open the fs, the inode is again full with invalid blocks. The affected inode was owned by file I've deleted some hours before sata-controller decided to write another file at invalid place, what leaded to errors in filesystem.
My question would be, why I can neither with debugfs, nor with fsck solve the problem of freeing an inode with invalid blocks? In particulary,
1) Why fsck seems to clear the inode, but after restarting finds again the next 11 invalid blocks?
2) Why debugfs after ignores freei and clri on this inode after close and open the affected fs?
Could you help me to solve this problem?
Thanks in advance!
P.S. I've used the 1.41.3 and also the most recent version 1.41.8 of e2fsprogs.