8

File System Checking - Best Practices

view full story
linux-howto

http://ubuntuforums.org – Is there any sense in running fsck -N first or should we just use -y right away and get it all over and done with fast? When we run fsck or e2fsck with the -y option and there are some serious file system problems, it silently unlinks any orphaned files to the lost+found. That's all fine and dandy when there's no big problems, normally no files need to be unlinked and fsck just runs and fixes the file system. When there are some problems, getting files back from the lost+found directory is probably not something most of us really want to spend time doing. They will be identified by inode n (Hardware)

linuxfan's picture
Submitted by linuxfan on 01/27/2013 – Made popular on 01/27/2013

Stories similar to File System Checking - Best Practices

I am a newbie in Linux. So this is my story

I installed Ubuntu server 10.04lts. It worked great for many months, until today i decided to run fsck on the system partition and although it warned me, I kept pressing yes and now it will only boot into grub prompt.

So i read some article and tried grub reinstall.

HOSTNAME:~ # fsck -n /FSMOUNTPOINT fsck 1.38 (30-Jun-2005) e2fsck 1.38 (30-Jun-2005) Warning!

My drive started to show up errors, I unmounted it and ran fsck on it. It's a 2TB drive installed on Debian Squeeze, using ext3.

The fsck too about 17 hours.

systemd-fsck boot message 30 weeks 6 days ago

fsck stands for "file system check" [1].  systemd will check all of your filesystems every time you boot [2].  systemd-fsck[145]: /dev/sda4: clean, 2977/296096 files, 85427/1217024 blocks systemd-fsck[151]: /dev/sda1: clean, 345/26104 files, 34083/104388 blocks (check after next mount)These messages mean that there are no problems with your filesystems and they are "clean&

File system repaired? 40 weeks 2 hours ago

Hello,

yesterday I made a backup onto my external harddisk (ext3 formatted) via rsync. After some time it returned

Code: rsync: stat "/media/my_harddisk/some/dir/foo.bar" failed: Input/output error (5) rsync error: some files could not be transferred (...) I then unmounted the disk and started fsck to check it. fsck told me, that the file system seems to be corrupt.

Possible Duplicate: How do you get e2fsck to show progress information?

Is there a way to check the progress of fsck.ext3 under Ubuntu, if I'm logged in remotely?

Obviously the time taken depends on a lot of factors, but if fsck has to option of displaying a progress bar, it should be possible

EDIT: Seems I didn't make the question clear enough.

I am using Ubuntu 12.04. Initially few days, everything worked fine, but then I started getting a problem quite frequently. After every 2-3 days, the file system becomes read-only. I am unable to save/download anything in the installation drive and the system hangs if I attempt to do so, after which I need to force restart. I have to run fsck in the repair mode to get it fixed.

Automatic fsck 42 weeks 6 days ago

From time to time it happens that I have a power failure and my computer shuts down uncleanly. Every time it happens, though, the next boot drops me into an emergency shell and tells me to run fsck manually. This has happened more than once, and each time the system boots fine after running fsck. When I used Ubuntu I never had to run it manually.

In the Linux operating system, fsck is a useful utility that scans the file system for consistency and integrity and on finding errors repairs them. It usually runs automatically at the time of startup if the system detects that the file system is in an inconsistent state. This utility runs both in interactive and non-interactive mode.