214 Part II . Getting Around in Linux (Best web hosting)
214 Part II . Getting Around in Linux Normally during system boot, fsck -pis run to check all file systems listed in the /etc/fstab file. This will automatically detect and fix problems with inodes, link counts, data blocks, and the superblock. If a more serious error is located, fsck -p will ask for help and then exit. Some of the errors that will cause this are as follows: . Blocks claimed by multiple files . Blocks claimed outside of the file system . Too few link counts . Unaccounted blocks . Directories that correspond to unallocated inodes . Format errors In cases where the parent directory of a file cannot be determined, the file will be placed in /lost+found. Files here are renamed with their inode numbers. Examining the contents of this directory can be useful when missing files after a system error. The exit information presented by the fsckutility provides useful information about the results of the operation. Each code represents a specific exit condition for the utility. The actual code returned is the sum of the exit conditions. The exit codes are displayed on the command line when the command has finished its operation. The exit codes are shown in Table 5-8. Table 5-8 fsck Exit Codes Code Meaning 1 File system errors corrected. 2 System should be rebooted. 4 File system error left uncorrected. 8 Operational error 0 No errors. 16 Usage or syntax errors. 128 Shared library error. The fsck utility should not be run on currently mounted devices. When checking a device it is recommended that you first unmount the device and then run fsck. The following examples show the correct use of the fsck utility. First, the drive is unmounted so that fsck can access the partition. The first example performs a
If you are in need for chaep and reliable webhost to host your website, our recommendation is http web server services.