Re: problem with corrupted filesystem

[Marcus Becker <Becker_Marcus1@web.de>]

Nothing wrong with it, just couldn't clean up afterwards. No crash etc.
emerge uses /var/tmp/portage as a build directory and when the binaries are finished it moves them to the live system and removes all files in there.
It cleans all other files/folders but cannot remove that folder (same as me).

Actual, I built gcc just again to see if the same happens again.
this time I ran it again after moving the folder to /root and without fsck. 
It ended up in a segmentation fault
Also I have another "locale" folder that cannot be removed.
Third time, same happens.

I'll now go ahead and do fsck again, remove those 2 folders and see afterwards if gcc builds fine again.

Always different inode, same problem with that "locale" folder
I can emerge other ebuilds without problems.

Cheers,

Marcus

-----Urspr