[SOLVED] Aborted journal and volume remounted read-only??
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I would guess that the first e2fsck you ran did that damage. That's why when you get an aborted journal you do _not_ run e2fsck first, you drop the journal. If I understand it correctly e2fsck tries to replay the aborted journal and then places the files in lost+found because of this.
Click here to see the post LQ members have rated as the most helpful post in this thread.
Not that I'm aware of. It's based on the inode numbers as the references got lost. You can use file to determine what kind of file it is and then look at the contents to put it back but I don't know about any programmatic way to accomplish that.
So will the files have the original filename or will the subfolders be the same as the original location? I had to step away for a bit so can't look, just trying to see how easy or difficult this might be
If I'm not mistaken it's because the directory entries got misplaced that the files are in the lost+found directory so the directory structure doesn't exist in lost+found. Just the files that didn't have any references. Once you do an ls on that directory you'll see if I'm correct.
When i do an ls in lost+found, all i see is those random inode names, which are guess are really files not folders for the most part. i guess i need to figure out how to do a ls that will only show me the folders it put in lost+found so i can cd into them and see what files are there. Then you were saying there is a way to tell what type of file all those files in there renamed with the inode name are?
You can use the file command to try and determine what format a file is in but it doesn't tell you the file name. The file name was part of the directory entry (directories are a special filesystem structure that correlates file names to inodes). I have the feeling there are no directories in your lost+found but to find out run the following:
find . -type d -print
If that comes back with any results at all they are directories otherwise everything else is a file.
Thanks. there are quite a few directories in there, maybe they have some files still that I could use and put back to where they should be. But that means that the majority of whats in the root of lost+found are files, which now have meaningless names to what they meant before Sounds like I'm kinda in a bad spot, right?
or i wonder if i could copy all them to my windows machine and use thumbnail view to see if any of these are actual jpgs to eliminate some? i think most of the files on the volume were jpg's to start with, so i'm guessing quite a few are them.
Thanks again, i think my best bet is to copy them all to my Windows PC so i can sift through them with a GUI. Couldn't have fixed this without you, wish i wouldnt have done the e2fsck first, i thought since the journal "aborted" it wouldn't use it when doing the e2fsck since it knew it was bad. guess not!