On Sat, Mar 29, 2008 at 12:44 PM, Peter Teoh <htmldeveloper@xxxxxxxxx> wrote: > Hi Katiyar, > > > > On Wed, Mar 26, 2008 at 2:48 AM, Manish Katiyar <mkatiyar@xxxxxxxxx> wrote: > > Apologies for spamming this list as this is not really a kernel > > question, but I could not find any appropriate list. Probably someone > > on this list with experience with e2fsprogs might help me. I was > > playing with the undelete option of debugfs. While trying to delete > > some file in ext3 and restore it this is what I did > > > > # dd if=/dev/zero of=testfs bs=4096 count=2000 > > # mkfs.ext3 testfs > > # sudo mount -t ext3 testfs mount -o loop > > #cd mount > > # echo manish > test > > # ls -alirt > > total 20 > > 11 drwx------ 2 root root 12288 2008-03-26 00:12 lost+found > > 3491025 drwxr-xr-x 3 mkatiyar mkatiyar 4096 2008-03-26 00:12 .. > > 14 -rw-r--r-- 1 mkatiyar mkatiyar 7 2008-03-26 00:13 test > > 2 drwxr-xr-x 5 mkatiyar mkatiyar 1024 2008-03-26 00:13 . > > # rm test > > # sudo umount mount > > # debugfs -w testfs > > debugfs 1.40.8 (13-Mar-2008) > > debugfs: lsdel > > Inode Owner Mode Size Blocks Time deleted > > 0 deleted inodes found. > > (END) > > debugfs: logdump > > Journal starts at block 0, transaction 8 > > > > Why is it still showing 0 deleted inodes ???? Should the deletion be > > shown in the journal ?? > > > > Any pointers to appropriate list will be helpful. Thanks > > > > I just attempted debugfs, which is freshly downloaded from > e2fsprogs.sourceforge.net website (it has enhanced support for Ext4). > I suspect the answer to your question is "time delay" (not sure > correct or not, but Ext4 offer > Hi Peter, Were you able to recover any files in ext3 using debugfs ?? Are you aware if debugfs or e2fsprogs supports recovery of files for ext3/ext4 filesystems ?? As far as I know it doesn't Thanks > This are my results: > > /download/e2fsprogs/e2fsprogs/debugfs>./debugfs > > debugfs 1.40.8 (13-Mar-2008) > debugfs: open /dev/sdb2 > > debugfs: lsdel > Inode Owner Mode Size Blocks Time deleted > 6146 0 100644 0 1019/ 1025 Sat Mar 29 14:41:14 2008 > 6164 0 100644 0 174/ 1025 Sat Mar 29 14:41:16 2008 > 6165 0 100644 0 182/ 1025 Sat Mar 29 14:41:16 2008 > 3 deleted inodes found. > > debugfs: lsdel > Inode Owner Mode Size Blocks Time deleted > 6164 0 100644 0 174/ 1025 Sat Mar 29 14:41:16 2008 > 6165 0 100644 0 182/ 1025 Sat Mar 29 14:41:16 2008 > 2 deleted inodes found. > > debugfs: lsdel > Inode Owner Mode Size Blocks Time deleted > 6164 0 100644 0 174/ 1025 Sat Mar 29 14:41:16 2008 > 6165 0 100644 0 182/ 1025 Sat Mar 29 14:41:16 2008 > 2 deleted inodes found. > > debugfs: lsdel > Inode Owner Mode Size Blocks Time deleted > 0 deleted inodes found. > > While on another terminal I will delete the files using "rm xxxx" for > files on the mounted filesystem. > > So the answer is that the kernel takes some time - not instantly > (which I suspect is a feature of Ext4?) before it display zero inodes > in the debugfs output. > > BTW (not sure if related or not), the string "testfs" you entered > above, may have to be corrected to "test_fs", as that is specifically > the string that mke2fs.c check for (search the e2fsprogs/misc > subdirectory). > > -- > Regards, > Peter Teoh > -- Thanks & Regards, ******************************************** Manish Katiyar ( http://mkatiyar.googlepages.com ) 3rd Floor, Fair Winds Block EGL Software Park Off Intermediate Ring Road Bangalore 560071, India *********************************************** -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
