Linux - GeneralThis 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.
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.
Most users are actually more interested in recovering their data than the science of recovering the filesystem itself. This is why fsck is so misunderstood.
See my sigline for an easier answer.
True but the OP might want to learn how to help with such problems, just like my ultimate dream is to be able to instantly and clearly fix any and every install and boot problem
If I wanted to play with filesystem recovery, what would be the best way to create a corrupted/damaged filesystem?
This paper includes a description of the methodology used:
Evaluating File System Reliability on Solid State Drives
Shehbaz Jaffer, Stathis Maneas, Andy Hwang, and Bianca Schroeder, University of Toronto
2019 USENIX Annual Technical Conference https://www.usenix.org/system/files/atc19-jaffer.pdf
It's quite an interesting paper.
Last edited by michael@actrix; 12-21-2021 at 05:07 PM.
Reason: typo
Most users are actually more interested in recovering their data than the science of recovering the filesystem itself. This is why fsck is so misunderstood.
No worries. I keep copious backups. And I plan to mess with a virtual drive/filesystem.
Quote:
Originally Posted by !!!
True but the OP might want to learn how to help with such problems, just like my ultimate dream is to be able to instantly and clearly fix any and every install and boot problem
Yes, it is my intention to learn more. I haven't experienced an actual corruption in many years. I figure I need to refresh my knowledge.
Right atm, I have a damaged filesystem. It's a Toshibs 2.5" platter in a usb3 case. The partition table vanished, so it wouldn't mount. I simulated making a partition, and it had a valid ext4 signature. It was a 600GB backup disk, but started identifying as 1TB
Using parted, I recovered a/the 600G partition, but couldn't mount it, because e2fsck was called for. To make a long story short, one of the bad blocks happens to be filesystem pivotal, and e2fsck kept pointlessly overwriting this, and everything else. Badblocks is chugging away atm.
I'm sure the data is gone, but I'm nearly alone in the world because I don't care. I have a backup of the backup for just this situation . So, what do you want to do?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
. So, what do you want to do?
