Linux - General This Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
|
08-29-2006, 04:13 PM
|
#1
|
Member
Registered: Aug 2005
Location: Sheffield, UK
Distribution: Gentoo
Posts: 105
Rep:
|
need to recover data in a deleted inode
I don't know whether "deleted inode" is quite correct, I'm not quite sure what that is even.
I finally finished the first two chapters of my book, and then I deleted it by accident
Now I scanned that area of the disk and found out what inodes the files were in, but I can't figure out how to get it back still.
I thought of using dd, but I don't know the absolute physical location of the files. How can you work this out?
|
|
|
08-29-2006, 04:19 PM
|
#2
|
LQ Guru
Registered: Dec 2005
Location: Somewhere on the String
Distribution: Debian Wheezy (x86)
Posts: 6,094
|
If it's a *.doc or *.txt type file, you might try recovering it with the program foremost. Just be sure to just search for doc type files (there's a cli option for that) so that you don't find all the other crap. You'll probably have to run it from a live CD or a separate filesystem...
|
|
|
08-29-2006, 04:56 PM
|
#3
|
Member
Registered: Aug 2005
Location: Sheffield, UK
Distribution: Gentoo
Posts: 105
Original Poster
Rep:
|
No, it's plaintext. The filenames are ./intro/01, ./intro/02, ./intro/03, ./intro/04, ./chooseday/05, and so on until ./chooseday/10.
|
|
|
08-29-2006, 05:16 PM
|
#4
|
LQ Guru
Registered: Dec 2005
Location: Somewhere on the String
Distribution: Debian Wheezy (x86)
Posts: 6,094
|
I'm pretty sure foremost will find those files. They'll be renamed some numeric combination though. You'll have to rename them once you recover them.
|
|
|
08-30-2006, 09:27 AM
|
#5
|
Member
Registered: Aug 2005
Location: Sheffield, UK
Distribution: Gentoo
Posts: 105
Original Poster
Rep:
|
Thanks for your replies, everyone.
I got my files back
Foremost scanned throguh my entire disk, making thousands of little files that I didn't want and had to sift through. I found it so frustrating that I didn't know which of these files I wanted, though I did know precisely where on the disk they were. I had their inode numbers which I found using debugfs.
MY SOLUTION: as always, google is my friend. I searched for something like "how to dump data from an inode" and it came up with an app called lde ( http://lde.sourceforge.net/). Using this I found my data and dumped them to files with ease.
Thanks again.
|
|
|
08-30-2006, 09:42 AM
|
#6
|
LQ Veteran
Registered: Aug 2003
Location: Australia
Distribution: Lots ...
Posts: 21,269
|
Glad to hear a success - I passed by there a year or so ago, but have never needed it.
One for the tool-box.
|
|
|
08-30-2006, 12:34 PM
|
#7
|
LQ Guru
Registered: Dec 2005
Location: Somewhere on the String
Distribution: Debian Wheezy (x86)
Posts: 6,094
|
Congratulations! Foremost does indeed scan the whole drive. The trick is to use the command line switch to only search for certain filetypes of bigger than a certain size.
But that other tool sounds like a good one to remember!
|
|
|
All times are GMT -5. The time now is 12:48 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|