> > By the way, there used to be undelete tool for ext2. It created a list
> > of deleted inodes with correct stat, but no names, only their inode
> > numbers. You could then pick the corect inode and give it a name, thus
> > bringing it back to life. Since ext3 is just ext2 with journal, I guess
> > it might work. It existed as a standalone tool and integrated to
> > midnight commander.
> I think there must be some other differences between ext2 and ext3, I've
> tryed e2undel and unrm, both made for ext2, and none of them found any
> deleted inode.
>
> I umonted immediately the drive, and nothing has been writen on it after
> the rm *
Maybe it's not working because you need to flush the journal before
the ext2 tool will see the inode as deleted. Alternatively, if that
is the case, perhaps by ignoring the data in the journal, the file
would not appear to be deleted.
Why not make a copy of the partition in to a file, and mount that file
using the loopback device - then you can try flushing the journal,
discarding the journal, etc.
John.
-
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/
This archive was generated by hypermail 2b29 : Tue Jan 07 2003 - 22:00:36 EST