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.
It is not advisable to mount it read only to fsck - it is advisable to unmount it completely. Run the fsck on the device not the mounted filesystem. (Use "df -h" to see what device is associated with the filesystem.)
What fsck will do depends much on what filesystem type you are running (Reiser? ext2? ext3? vxfs? something else?) but in general it can screw things up pretty badly if it is mounted r/w.
Do you have VMSA (usually in /opt/VRTSvmsa) on the server or VEA on a Windows machine? If so you might want to see what options those give you. We're running some old HP-UX and in VEA the "check filesystem" is greyed out for me but you might have a newer version that allows for checking (if any do). There a quite a few things that can be done on line if you're running Veritas Volume Manager in addition to Veritas Filesystem (e.g. adding new disk to the volume and evacuating data from the old one to the new one - might help if you suspect a disk issue).
I actually got it working by moving the disks to a new server, not entirely sure why but it didn't require a manual fsck when I switched the disks over. Think it was my var partition that needed the fsck but thats no longer an issue. I guess I can resolve this, still sorta interested in what happens though. If this is such a dangerous thing to do why does fsck even give the option. I guess the effects would be dependant upon which files were fragmented (e.g if the contents of /tmp were fragmented and required an fsck and it was run on a read only partition I suspect it wouldn't have a noticable effect where as if it were /home it might...).