Hello, We have run and stopped by chance command "fsck -y" on one of our raid disks (with ext3 file system). After that we have found that SOME files disappeared (they are not seen in the directories where they have been before). The data are extremely important and contain a lot of programs, scripts for some data analysis and very hard to recover by hands. I have run ''fsck -y" once more and it recovered just few files.. Is there any way, any tool that would allow to recover the data? Probably there is some specific options for the recovery ralated with journaling in ext3? I have used debugfs, it produced following, if it helps: debugfs: open -f -w /dev/sdb1 debugfs: features Filesystem features: has_journal resize_inode filetype needs_recovery sparse_super large_file thanks, Dmitry
On Tue, 25 Jul 2006 at 7:27pm, Dmitry Bandurin wrote> We have run and stopped by chance command "fsck -y" on one of our raid disks > (with ext3 file system). After that we have found that SOME files disappeared > (they are not seen in the directories where they have been before). > The data are extremely important and contain a lot of programs, > scripts for some data analysis and very hard to recover by hands. > I have run ''fsck -y" once more and it recovered just few files.. > Is there any way, any tool that would allow to recover the data? > Probably there is some specific options for the recovery ralated with > journaling in ext3?Have you looked in the lost+found directory? That's my only idea, other than recovering the files from your backups. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
http://batleth.sapienti-sat.org/projects/FAQs/ext3-faq.html ---- Q: How can I recover (undelete) deleted files from my ext3 partition? Actually, you can't! This is what one of the developers, Andreas Dilger, said about it: 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. Your only hope is to "grep" for parts of your files that have been deleted and hope for the best. ---- You can try to contact Andreas Dilger and maybe he can help. adilger at clusterfs.com Mr. X Dmitry Bandurin wrote:> Hello, > > We have run and stopped by chance command "fsck -y" on one of our raid > disks > (with ext3 file system). After that we have found that SOME files > disappeared > (they are not seen in the directories where they have been before). > The data are extremely important and contain a lot of programs, > scripts for some data analysis and very hard to recover by hands. > I have run ''fsck -y" once more and it recovered just few files.. > Is there any way, any tool that would allow to recover the data? > Probably there is some specific options for the recovery ralated with > journaling in ext3? > > I have used debugfs, it produced following, if it helps: > debugfs: open -f -w /dev/sdb1 > debugfs: features > Filesystem features: has_journal resize_inode filetype needs_recovery > sparse_super large_file > > > thanks, > Dmitry > > _______________________________________________ > Ext3-users mailing list > Ext3-users at redhat.com > https://www.redhat.com/mailman/listinfo/ext3-users >
On Tue, Jul 25, 2006 at 07:27:11PM -0500, Dmitry Bandurin wrote:> The data are extremely important and contain a lot of programs, > scripts for some data analysis and very hard to recover by hands.maybe it could help: http://dirk.eddelbuettel.com/blog/2006/07/20#ext3_undelete ciao, gelma
On Tue, Jul 25, 2006 at 07:27:11PM -0500, Dmitry Bandurin wrote:> Hello, > > We have run and stopped by chance command "fsck -y" on one of our raid disks > (with ext3 file system). After that we have found that SOME files > disappeared > (they are not seen in the directories where they have been before). > The data are extremely important and contain a lot of programs, > scripts for some data analysis and very hard to recover by hands. > I have run ''fsck -y" once more and it recovered just few files.. > Is there any way, any tool that would allow to recover the data? > Probably there is some specific options for the recovery ralated with > journaling in ext3? > > I have used debugfs, it produced following, if it helps: > debugfs: open -f -w /dev/sdb1 > debugfs: features > Filesystem features: has_journal resize_inode filetype needs_recovery > sparse_super large_fileYou could look at my patched version of debugfs - http://std.dkuug.dk/keld/readme-salvage.html Best regards Keld