7 Jun
2007
7 Jun
'07
8:46 p.m.
Christophe HENRY wrote:
In order to ensure that ext3 can safely resume an
unlink after a crash,
it actually zeros out the block pointers in the inode, whereas
ext2 just marks these blocks as unused in the block bitmaps and marks
the inode as "deleted" and leaves the block pointers alone.
Actually this is a very interesting fact. When I migrated from ext2 to
ext3 years ago, I was convinced (actually until now) that it would be
possible to use the ext2 undelete tools for a ext3 partition. One of the
main advantages of ext3 in comparison to jfs, xfs, reiserfs was the ext2
compatibility. A recovery disc with only ext2 support should be able to
mount ext3 partitions by ignoring the ext3 journal in the hidden blocks.
Even a fsck.ext2 should work. But unfortunately the undelete tools do
not work, a fact I was not aware of!
Greetings, Patrick