fsck

In contrast, ReiserFS' fsck is in its infancy, and fixing flaky metadata when it does show up can be a difficult and dangerous process.

So, now you know for whom journaling file systems were created, but how do they obviate the need for fsck?

fsck's job is to ensure that the to-be-mounted filesystems' meta-data is in a usable state.

In most cases, it's necessary to run fsck or its helper program on an unmounted file system.

Rather than restoring the system or even rebuilding the operating system, you can use fsck to repair file systems or correct damaged inodes.

man fsck and info fsck provide details, as do several of the Resources included at the end of this article.

And unlike the more traditional approach that fsck takes, this journal replaying process does not take longer on larger filesystems.

That's one of the things done by fsck, the filesystem consistency checking program.

The other aspect of online defragmentation is the reduced time required for a file system check (fsck).

fsck must be run on unmounted volumes, though it is rarely needed unless the file system was not cleanly unmounted.

And the best strategy for fixing file system issues is the simplest: the file system check command (fsck).

Ext4 marks unused groups of blocks within the inode table to allow the fsck process to skip them entirely to speed the check process.

Journalling filesystems solve this fsck problem by adding a new data structure, called a journal, to the mix.

So, what does fsck do with a journalling filesystem?

By using the fsck command, you can narrow the search for damaged inodes, as well.

If you're searching for a specific inode, you can use the -ii-NodeNumber switch with fsck.

Problems arise from the fact that fsck must scan a filesystem's entire meta-data in order to ensure filesystem consistency.

Check the documentation for your file system-specific fsck helper program to learn about its options.

Once fsck is complete, the filesystem is ready for use.

That certainly beats the fsck process.

If your filesystems weren't unmounted cleanly, you should fsck them first.

Internal snapshots are removed if the fsck command has to modify a JFS2 file system to repair it.

Unmount the filesystem and fsck and re-mount it.

Maybe you're using a journalling filesystem such as ReiserFS to reduce fsck time and increase filesystem reliability and performance.

It's based on the solid ext2 filesystem code and it inherits a great fsck tool.

The fsck utility, however, is mainly a front-end to file system-specific tools, such as e2fsck (for ext2fs, ext3fs, and ext4fs).

You should check the file system consistency for each file system. You can do this with the fsck command

The one solution to both scenarios is running fsck, as follows

an AIX command (e. g. fsck) is taking a long time to complete, or has hung