Hi,

I had a filesystem with lots of errors, among them multiply-used
blocks. fsck.ext4 run fine and detected 179 inodes with multiply-used
blocks but then it started to clone files to fix those inodes. Every
3-4 hours it fixes one inode and just burns 100% cpu inbetween. Strace
shows no syscalls being made and it isn't swapping. It just sits there
and eats cpu.

Running an older fsck from grml (1.41) took less than a second per
inode.

As a side note I think resize2fs has the same issue. After pass 3
"Scanning inode table" it just sits there for a while also eating 100%
cpu before it continues.

MfG
	Goswin