un'stat'able files - fs corruption?

[Stephen Samuel]

When you ran the FSCK, did you force the check ( -f )?
Usually fsck will refuse to run a full test if it thinks that the filesystem
was unmounted
cleanly or if it thinks that running the log will be sufficient cleanup.

Also, have you moved this filesystem between machines (and, most notably,
between architectures)?

On Thu, Feb 12, 2009 at 5:41 AM, Jochen Rueter <
joschi at fliegergruppe-donzdorf.de> wrote:

> My e2fsck is version e2fsck 1.40-WIP (14-Nov-2006), which is included in
> debian lenny.
> Actually, ls seems even not to be able to determine the inode number:
>
> 21022170 -rwxrwxr-x 1 yvonne users    30208 2007-09-16 12:49
> Stoffverteilungsplan tw kl4 07.doc
>      ? ?--------- ? ?      ?            ?                ? Termine für
> Dienstag kiga.doc
>
> Maybe it's worth noting that this is running on arm: 2.6.21 #1 PREEMPT Tue
> May 8 21:05:53 CEST 2007 armv5tel GNU/Linux
>
> Jochen
>
> Christian Kujau schrieb:
>
>> On Mon, 9 Feb 2009, Jochen Rueter wrote:
>>
>>
>>> ?--------- ? ?      ?            ?                ? Teddyb?r.docx
>>> ?--------- ? ?      ?            ?                ? Termine f?r montag
>>>
>>>
>> [...]
>>
>>
>>> Also e2fsck does not find any errors on this filesystem.
>>>
>>>
>>

-- 
Stephen Samuel http://www.bcgreen.com
778-861-7641
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/ext3-users/attachments/20090213/f59100b6/attachment.htm>