On Wed, 21 Mar 2001, Andreas Dilger wrote:
> > debugfs: stat 199908231702.txt
> > Inode: 1343489 Type: bad type Mode: 0000 Flags: 0x0
> > Version/Generation: 0
> > User: 0 Group: 0 Size: 0
> > File ACL: 0 Directory ACL: 0
> > Links: 0 Blockcount: 0
> > Fragment: Address: 0 Number: 0 Size: 0
> > ctime: 0x00000000 -- Wed Dec 31 19:00:00 1969
> > atime: 0x00000000 -- Wed Dec 31 19:00:00 1969
> > mtime: 0x00000000 -- Wed Dec 31 19:00:00 1969
> > BLOCKS:
>
> Maybe you really _are_ having I/O errors? That would explain the zero'd
> inode table and the I/O error messages.
*shrug* Maybe. This is beyond the scope of what I know but I'm trying to
learn.
If no one else wants anything, I'll be reformatting that partition
tonight after seeing what fsck does.
--
=====================================================================
Mohammad A. Haque http://www.haque.net/
[EMAIL PROTECTED]
"Alcohol and calculus don't mix. Project Lead
Don't drink and derive." --Unknown http://wm.themes.org/
[EMAIL PROTECTED]
=====================================================================
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
