HOSTNAME:~ # fsck -n /FSMOUNTPOINT fsck 1.38 (30-Jun-2005) e2fsck 1.38 (30-Jun-2005) Warning! /dev/vgname/lvname is mounted. Warning: skipping journal recovery because doing a read-only filesystem check. /dev/vgname/lvname contains a file system with errors, check forced. Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Inode 12845121 ref count is 1, should be 2. Fix? no Inode 12845122 ref count is 1, should be 2. Fix? no Inode 12845123 ref count is 1, should be 2. Fix? no Inode 12845124 ref count is 1, should be 2. Fix? no Pass 5: Checking group summary information Free blocks count wrong (38829073, counted=37828469). Fix? no Free inodes count wrong (22658484, counted=22658235). Fix? no /dev/vgname/lvname: ********** WARNING: Filesystem still has errors ********** /dev/vgname/lvname: 16972/22675456 files (0.3% non-contiguous), 6521839/45350912 blocks fsck.ext3 /dev/vgname/lvname failed (status 0x4). Run manually! HOSTNAME:~ #
OS: SUSE LINUX Enterprise Server 9.4
FS: EXT3 with only rw options
Question: So if there is the "WARNING: Filesystem still has errors" message, I can be 100% sure that the FS has problems, and needs to be umount/fsck/mount'ed?
$ tune2fs -l /dev/vgname/lvname | grep 'Filesystem state:' Filesystem state: clean $