Become superuser or assume an equivalent role.This procedure assumes that a local Solaris DVD or network boot server isĪvailable so that you can boot the system from an alternate device.įor information on restoring a bad superblock, see How to Restore a Bad Superblock (Solaris 10 6/06 Release) or How to Restore a Bad Superblock (Solaris 8, 9, and 10 Releases). This message is just informational about fsck's corrective actions. However, it doesn't harm the file system to rerun fsck after this message. There is no need to rerun fsck if you see the following message: ***** FILE SYSTEM WAS MODIFIED ***** How to Check the root ( /), /usr, or /var File Systems From an Alternate Boot Deviceįor new information about fsck in the Solaris 10 6/06 release, see Enhancements to UFS File System Utilities ( fsck, mkfs, and newfs). If you need to repair the root ( /), /usr, and /var file systems, boot the system from an alternate device, if possible, so that these file systems are unmounted and inactive.įor step-by-step instructions on running fsck on the root ( /), /usr, or /var file systems, see How to Check the root ( /), /usr, or /var File Systems From an Alternate Boot Device. The only exceptions are for the active root ( /), /usr, and /var file systems because they must be mounted to run fsck. Doing so ensures that the file system data structures are consistent as possible. Unmount a file system before you use fsck on that file system. Or, they might cause the system to crash. File system changes waiting to be flushed to disk or file system changes that occur during the fsck repairing process might cause the file system to become corrupted. These issues may not be a reliable indication of a problem.Ī file system must be inactive when you use fsck to repair that file system. File system changes waiting to be flushed to disk or file system changes that occur during the fsck checking process can be interpreted as file system corruption. Keep the following points in mind when running the fsck command to checkĪ file system should be inactive when you use fsck to check a file system. Hostname is the system reporting the error.īefore using the fsck command, you might want to refer to these referencesįor information on resolving fsck error messages:Ĭhapter 20, Resolving UFS File System Inconsistencies (Tasks), in System Administration Guide: Advanced Administration The following: Sep 5 13:42:40 hostname ufs: NOTICE: /: unexpected Or, the system might crash.įor example, the system messages file, /var/adm/messages, might include messages similar to The console window or the system messages file. When an in-use file system develops inconsistencies, error messages might be displayed in When they develop inconsistencies while in use You might need to interactively check file systems in the following instances: Interactively Checking and Repairing a UFS File System ![]() UFS Components That Are Checked for Consistencyįile System Size and Inode List Size Checks Why UFS File System Inconsistencies Might Occur What the fsck Command Checks and Tries to Repair Checking UFS File System Consistency (Tasks) Configuring Additional Swap Space (Tasks)Ģ1. Mounting and Unmounting File Systems (Tasks)ġ9. Creating ZFS, UFS, TMPFS, and LOFS File Systems (Tasks)ġ8. Configuring Oracle Solaris iSCSI Targets and Initiators (Tasks)ġ7. Using InfiniBand Devices (Overview/Tasks)ġ4. ![]() Dynamically Configuring Devices (Tasks)ĩ.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |