Actuall, e2fsck can also do the journal replay, so depending on whether this
is the root fs or not, it may be that you get a journal replay and still
mount it as ext2...
> So, AFTER a journal replay, there were still two damaged inodes
> - which sounds like Anton's problem. Maybe ext3 just hates Cambridge? :-)
Well, if you had a SCSI error, then it may be that the fs marked an error
in the superblock, which would force a full fsck also.
Note also, that it is often normal to have "orphaned inodes" cleaned up when
the journal is cleaned up. This is not an error. I normally have these on
my system because of PCMCIA cardmgr creating device inodes in /tmp and then
unlinking them immediately after opening them.
If you have an open but unlinked file, then ext3 will delete this file at
mount/fsck time (unlike reiserfs which leaves it around wasting space).
Did you actually get files in lost+found, or only the orphaned inode
message?
Cheers, Andreas
-- Andreas Dilger http://sourceforge.net/projects/ext2resize/ http://www-mddsp.enel.ucalgary.ca/People/adilger/- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/