On 07/12/2014 08:31 PM, Carlos E. R. wrote:
Meaning that fsck is broken itself, too. :-/
Not broken: inadequate. See things like http://lde.sourceforge.net/lde_man.txt You need to use something like http://linux.about.com/library/cmd/blcmdl8_debugfs.htm to zap the inode and then use fsck to clean up the blocks that don't seems to be allocated to any inode ... That is the ones that might have been or might not have been to the zapped inode. Thinks: if the corrupted node appears to point its 'file' to blocks that actually belong to another file, then fsck will see them as belonging to that other file. See also http://serverfault.com/questions/315700/how-to-determine-which-file-inode-oc... which can lead to some interesting details of 'under the hood' -- /"\ \ / ASCII Ribbon Campaign X Against HTML Mail / \ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org