Scribd
Upload
126 views

FSCK Process

The document discusses the fsck process in Solaris and provides tips for fixing common fsck errors. It should not be run on a mounted filesystem as it may produce errors. For the root filesystem, the OS runs fsck automatically at boot by mounting read-only, running fsck, and then remounting read-write. To manually fsck the root filesystem, one should boot from the installation CD and fsck the hard disk from there.

Uploaded by

api-3701740
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
126 views

FSCK Process

The document discusses the fsck process in Solaris and provides tips for fixing common fsck errors. It should not be run on a mounted filesystem as it may produce errors. For the root filesystem, the OS runs fsck automatically at boot by mounting read-only, running fsck, and then remounting read-write. To manually fsck the root filesystem, one should boot from the installation CD and fsck the hard disk from there.

Uploaded by

api-3701740
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 1

fsck Process

by Jeff Hunter, Sr. Database Administrator

It's not uncommon under Solaris to get some fsck errors, especially if you powered off a
machine without doing a proper shutdown (or it crashed). The "FREE BLKS" errors is
extremely minor, you can safely just say "Y" to fixing those errors. This shouldn't happen
every time you boot, though, unless you aren't shutting down properly. It's also possible
to say "fsck -y" and then it will fix everything without prompting you.

Do not try to fsck a currently mounted filesystem - that will always produce an error
(and is a bad idea) because the filesystem data structures are "open" and there may be
changes in memory that have not been written to the disk yet. The proper way is to fsck
a filesystem when it's not mounted. How do you do that if it's the root filesystem you
want to fsck? Well, the OS does it at boot by mounting / readonly, fscking it, and then
remounting it read/write. My approach would be to boot off the CD ("boot cdrom -s, or
boot -s cdrom, from the ok prom prompt) and then fsck the hard disk.

You might also like