I might be wrong here, but as far as I unsderstand, ext3 is EXACTLY the same as ext2 but with Journalising.
ext2 systems can read ext3 disks and vice versa. Surely this means that undeleteing ext3 uses the same method as ext3 (Journalising does not come into it as that only has to do with at what time the data is writen to disk. Assuming you cleanly unmounted your fs, the data would be the same on the disk whether you are using ext2 or ext3)

Try these HOW-TOs from The Linux Documentation Project: (I have never used these particular howtoos, so ur on your own there...)

http://www.tldp.org/HOWTO/Ext2fs-Undeletion.html
http://www.tldp.org/HOWTO/Ext2fs-Undeletion-Dir-Struct/index.html

Quote:
I might be wrong here, but as far as I unsderstand, ext3 is EXACTLY the same as ext2 but with Journalising.
ext2 systems can read ext3 disks and vice versa. Surely this means that undeleteing ext3 uses the same method as ext3 (Journalising does not come into it as that only has to do with at what time the data is writen to disk. Assuming you cleanly unmounted your fs, the data would be the same on the disk whether you are using ext2 or ext3)

Quote:
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 he inode as 'deleted' and leaves the block pointers alone. Your only hope is to 'grep' for parts of your files that have been deleted and hope for the best.