Re: ext3 filesystem which can't be corrected?

[Tomasz Chmielewski <mangoo@wpkg.org>]

Andreas Dilger schrieb:
> On Apr 02, 2008  17:03 +0200, Tomasz Chmielewski wrote:
>> Let's see what we have there - four files with exactly the same name and 
>> inode:
>>
>> # ls -li
>> total 16
>> 73793642 -rw-r----- 179 backuppc backuppc 46 May 14  2007 attrib
>> 73793642 -rw-r----- 179 backuppc backuppc 46 May 14  2007 attrib
>> 73793642 -rw-r----- 179 backuppc backuppc 46 May 14  2007 attrib
>> 73793642 -rw-r----- 179 backuppc backuppc 46 May 14  2007 attrib
>>
>>
>> Let's remove "attrib" file:
>>
>> # rm -f attrib
>>
>> Ouch:
>>
>> # ls
>> ls: attrib: No such file or directory
>> ls: attrib: No such file or directory
>> ls: attrib: No such file or directory
>>
>> When I want to browse the directory i.e. in midnight commander (mc), it 
>> shows me three files in red called "?attrib", dated 1 Jan 1970.
> 
> Looks like it has unprinting characters.  Try
> find . -print0 | xargs -0 rm

Nope, that's something else.
Several files in the same directory which had the same inode number and 
the same name.


>> e2fsck comes from e2fsprogs 1.39 - should I try something newer?
> 
> It is usually best to use the latest version.

True, but the filesystem check takes 8 hours or so here, so I can't 
start it unless a disaster happens.


-- 
Tomasz Chmielewski
http://wpkg.org