Filesystem errors, how do I tell which volume its on from log errors?
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.
Of course, looking into the /dev folder can help you find the devices in question as well...
This should happen when a fils sys check is forced (on my box it's done every so mounts) so a /dev/sdasomething should have been on the screen...
Hope (sincerely) to have helped a bit, if not, do ignore my post, thanks. ;-)
Right, I planned on running it against all of them, but if i can minimize the downtime by taking a volume or two down before shutting the whole thing down and get those checked, that could save me hours, especiall if e2fsck needs to make multiple passes to fix it.
Multiple passes fixing errors vs. one pass because its already clean could save me a few hours of downtime when I do take the server down. I'm dealing with extremely large volumes here.