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.
last night my server crashed. it is responsible for backup of another server, using rsync over ssh. the disk has three partitions: boot, swap, and /
the / partition is an ext3 filesystem. i was getting the following error on the console when i noticed the machine was not responding when I tried to ssh to it:
EXT3-fs error (device hda3) in stat_transaction: journal has aborted
this error kept coming up on the console screen continuously. I tried rebooting and got the message the ext3 system had errors, and i entered root console mode to fix the filesystem. unfortunately I couldn't unmount it since all software was on it, so I rebooted using a live CD, unmounted the filesystem, and then ran fsck to fix it.
i kept answering yes to fix all errors (it asked to link nodes to /lost+found several times, as well as reporting empty nodes which it asked to clear).
after that, the system rebooted fine, and everything seems to be working ok, but I'm a little worried now that some of my data or software is gone and I still need to fix more. how do I find out what I need to fix now on my system?
I found a lot of files in /lost+found now, but not sure what to do with them or to find out what files they used to belong to.
Data is written twice on the harddisk: in the filesystem and then in the journal. After the write process is commited (performed), the journal is cleared.
Data stored in lost+and are files, where the write porcess is not performed. You may try to recover them, but you should not do that.