In this article we will see how can we setup repair to LINUX file system.
There are certain levels where your file system can be crash.
1- any mount point is crashed.
2- your device mount point is crashed.
3- your boot level is crashed.
in LINUX whenever your mount point is crashed you can’t get access to the particular device
but if your boot is crashed you can’t access to your LINUX box and everytime you boots up it will take you to the shell prompt where it asking you to repair your file system if you don’t do right now you can’t get access.
there are some certain ways to repair you file system.
fsck is used to check and optionally repair one or more Linux file systems. filesys can be a device name (e.g. /dev/hdc1, /dev/sdb2), a mount point (e.g. /, /usr, /home), or an ext2 label or UUID specifier (e.g. UUID=8868abf6-88c5-4a83-98b8-bfc24057f7bd or LABEL=root). Normally, the fsck program will try to handle filesystems on different physical disk drives in parallel to reduce the total amount of time needed to check all of the filesystems.
If no filesystems are specified on the command line, and the -A option is not specified, fsck will default to checking filesystems in /etc/fstab serially. below ar ethe switshes to repair filesystem manually
there are some parameter you can use to repair you linux filesystem accordingly
fsck -r (it repair file sys interactively)
fsck -y (it will check corruption and fix it automatically in interactively)
fsck -f (it will repair force fully)
fsck -a (it will repair without asking)
- Understanding /etc/fstab file in linux (alexhunt86.wordpress.com)
- JFS Filesystem (wiki.archlinux.org)
- Pass BrowserContext to drive::MountPointProviderDelegate. (chromiumcodereview.appspot.com)