Red Hat Linux Troubleshooting – File system Errors


I have started ( aka in 2009 as my own personal reference blog, and later sometime i have realized that my leanings might be helpful for other unixadmins if I manage my knowledge-base in more user friendly format. And the result is today's' You can connect me at -

Loading Facebook Comments ...

3 Responses

  1. marty says:

    I tend to think multiuser, so that influences my point of view..

    With #11, I’d never mount a filesystem I didn’t know was good with its original name, unless forced to (/opt, or something like that). So I’d create another mount point and mount that problem volume with a new name, until I’d sorted things out (fixed it or tossed it, or very occasionally salvaged what we could).

    With #9, I might point out “fsck -y” to those who might not be aware of it. If the filesystem has *a lot* of problems manually may not be reasonable/possible. So “fsck”, then “fsck -y” if you have to.

    With at least one flavor of unix/filesystem combinations I’ve seen in the past, the superblock locations got recorded in a file (/etc/superblock, I think), and I got lucky using some of those other superblocks when the first didn’t work. Rare, but one does get desperate. It has been a very long time since this has come up for me.

  1. July 22, 2016

    […] Read – Red Hat Linux Troubleshooting – File system Errors […]

Leave a Reply

Your email address will not be published. Required fields are marked *

[contact-form to='' subject='New Learning Request Submitted'][contact-field label='Name' type='name' required='1'/][contact-field label='Email' type='email' required='1'/][contact-field label='Learning Request' type='textarea' required='1'/][contact-field label='Are you Looking for ' type='radio' required='1' options='Paid Training,Free Training'/][/contact-form]

What is your Learning Goal for Next Six Months ? Talk to us