[Extundelete-users] extundelete on Ext4
Status: Beta
Brought to you by:
necase
From: <ext...@li...> - 2009-07-28 12:07:17
|
Unfortunately I'm here... After almost 20 years of intense computer use, I did my first \rm -rf * in the wrong directory ! I deleted some directories that I'd like to recover in my home dir. But Fortunately you are here too... I did use extundelete0.1.1 (after a rapid compilation on my computer). Using the option --restore-all: extundelete012 /dev/mapper/VolGroup-lv_user --restore-all Obviously extundelete recovers some files and directories and also their name but it suddenly stops with the following message: (...) Restored inode 2784 to file RECOVERED_FILES/home/bruno/.gimp-2.6/environ/b Restored inode 2785 to file RECOVERED_FILES/home/bruno/.gimp-2.6/environ/glnx86 Restored inode 2770 to file RECOVERED_FILES/home/bruno/.gimp-2.6/scripts/tar.enc Restored inode 2773 to file RECOVERED_FILES/home/bruno/.gimp-2.6/templates/tar.cmp Restored inode 2774 to file RECOVERED_FILES/home/bruno/.gimp-2.6/templates/b *** glibc detected *** extundelete: free(): invalid next size (fast): 0x096f58c0 *** ======= Backtrace: ========= /lib/libc.so.6[0x2d8231] /usr/lib/libstdc++.so.6(_ZdlPv+0x21)[0x34543f1] /usr/lib/libstdc++.so.6(_ZdaPv+0x1d)[0x345444d] extundelete[0x804d905] extundelete[0x804d6c5] extundelete[0x805a833] extundelete[0x804d8af] extundelete[0x804d6c5] extundelete[0x805a833] extundelete[0x804d8af] extundelete[0x804d6c5] extundelete[0x805a833] extundelete[0x804d8af] extundelete[0x804d6c5] extundelete[0x805a833] extundelete[0x804d8af] extundelete[0x804d6c5] extundelete[0x805a833] extundelete[0x804d8af] extundelete[0x804e656] extundelete[0x804f750] extundelete[0x804b53d] /lib/libc.so.6(__libc_start_main+0xe6)[0x27ea66] extundelete[0x804a801] ======= Memory map: ======== 00244000-00264000 r-xp 00000000 fd:00 131602 /lib/ld-2.10.1.so 00264000-00265000 r--p 0001f000 fd:00 131602 /lib/ld-2.10.1.so 00265000-00266000 rw-p 00020000 fd:00 131602 /lib/ld-2.10.1.so 00268000-003d3000 r-xp 00000000 fd:00 131605 /lib/libc-2.10.1.so 003d3000-003d4000 ---p 0016b000 fd:00 131605 /lib/libc-2.10.1.so 003d4000-003d6000 r--p 0016b000 fd:00 131605 /lib/libc-2.10.1.so 003d6000-003d7000 rw-p 0016d000 fd:00 131605 /lib/libc-2.10.1.so 003d7000-003da000 rw-p 003d7000 00:00 0 003dc000-00402000 r-xp 00000000 fd:00 131619 /lib/libm-2.10.1.so 00402000-00403000 r--p 00025000 fd:00 131619 /lib/libm-2.10.1.so 00403000-00404000 rw-p 00026000 fd:00 131619 /lib/libm-2.10.1.so 0040d000-00423000 r-xp 00000000 fd:00 131606 /lib/libpthread-2.10.1.so 00423000-00424000 ---p 00016000 fd:00 131606 /lib/libpthread-2.10.1.so 00424000-00425000 r--p 00016000 fd:00 131606 /lib/libpthread-2.10.1.so 00425000-00426000 rw-p 00017000 fd:00 131606 /lib/libpthread-2.10.1.so 00426000-00428000 rw-p 00426000 00:00 0 006e3000-006e4000 r-xp 006e3000 00:00 0 [vdso] 00821000-0084d000 r-xp 00000000 fd:00 100668 /lib/libext2fs.so.2.4 0084d000-0084e000 rw-p 0002c000 fd:00 100668 /lib/libext2fs.so.2.4 009d1000-009d3000 r-xp 00000000 fd:00 100560 /lib/libcom_err.so.2.1 009d3000-009d4000 rw-p 00001000 fd:00 100560 /lib/libcom_err.so.2.1 03372000-0339c000 r-xp 00000000 fd:00 131659 /lib/libgcc_s-4.4.0-20090506.so.1 0339c000-0339d000 rw-p 00029000 fd:00 131659 /lib/libgcc_s-4.4.0-20090506.so.1 0339f000-03482000 r-xp 00000000 fd:00 131660 /usr/lib/libstdc++.so.6.0.11 03482000-03486000 r--p 000e2000 fd:00 131660 /usr/lib/libstdc++.so.6.0.11 03486000-03488000 rw-p 000e6000 fd:00 131660 /usr/lib/libstdc++.so.6.0.11 03488000-0348e000 rw-p 03488000 00:00 0 08048000-08065000 r-xp 00000000 fd:00 100671 /usr/bin/extundelete 08065000-08066000 rw-p 0001c000 fd:00 100671 /usr/bin/extundelete 094c9000-09785000 rw-p 094c9000 00:00 0 [heap] b7d1b000-b7f6a000 rw-p b7d1b000 00:00 0 b7f7e000-b7f7f000 rw-p b7f7e000 00:00 0 bfd87000-bfd9c000 rw-p bffeb000 00:00 0 [stack] Aborted [root@localhost extundelete_result]# ---------------------------------------------------- I tried after that version 0.1.2 of extundelete after compiling the e2fsprogs1.41.8 latest version. This time there is no sudden abort, version 1.41.8 seems to go farther and identify other files and directories but does not create any file or directory in the RECOVER directory since I always get the same type of message: Unable to restore inode #### (home/.../mpgwrite/mpgwrite.mexsol.gz): No data found. while version 0.1.1 is able to recover correctly. It maybe a problem in the installation of the latest version of e2fsprogs, I'm not sure of what I did. I use FedoraCore 11. I also tried photorec. It's able to recover many, many files, even old files of a previous (now deleted) partition (ext3 probably) of my dis! But I miss the names, they are "randomly" sorted, and not all recovered since only some (a lot though :) file types are detected. That is why I wanted to test extundelete whose philosophy is not the same. Since extundelete0.1.1 gives promising results, does anyone has any idea of the error: *** glibc detected *** extundelete: free(): invalid next size (fast): 0x096f58c0 *** Is there a way to fix that ? Thanks! bruno (I don't know much about file systems...) :-) ____________________________________________________ Le week-end sera pluvieux ? Quel dommage !... Mais pas de panique le nouveau Guide TV de Voila est là http://tv.voila.fr |