On 6/3/13 2:29 PM, Autif Khan wrote: > On Mon, Jun 3, 2013 at 3:13 PM, Eric Sandeen <sandeen@xxxxxxxxxx> wrote: >> On 6/3/13 1:45 PM, Autif Khan wrote: >>> Executing dumpe2fs -h on one of the partitions says >>> >>> ... >>> Filesystem features: has_journal ext_attr resize_inode dir_index >>> filetype extent flex_bg sparse_super large_file huge_file uninit_bg >>> dir_nlink extra_isize >>> Filesystem flags: signed_directory_hash >>> Default mount options: user_xattr acl >>> Filesystem state: clean with errors >>> ... >>> >>> How can I find out what the errors are - the details of the errors. >> >> "clean" means the log has been replayed (log is not dirty) >> "with errors" means that it encountered concistency errors at runtime >> >> run e2fsck -f on it to see what it finds (or e2fsck -fn if you want a no-op >> dry run) > > --- spin --- > > ubuntu@mac0013950af6fb:~$ sudo fsck -V -n -f /dev/sda5 > fsck from util-linux 2.20.1 > [/sbin/fsck.ext4 (1) -- /koko] fsck.ext4 -n -f /dev/sda5 > e2fsck 1.42 (29-Nov-2011) > Warning! /dev/sda5 is mounted. Surprising that it didn't find errors since you ran it on a mounted fs! That's also an older e2fsck, so I suppose it's possible that it missed something. > Pass 1: Checking inodes, blocks, and sizes > Pass 2: Checking directory structure > Pass 3: Checking directory connectivity > Pass 4: Checking reference counts > Pass 5: Checking group summary information > /dev/sda5: 24770/262144 files (0.1% non-contiguous), 328031/1048576 blocks > ubuntu@mac0013950af6fb:~$ > > I am not sure I see any errors. Is there an error here? No, that didn't report any errors. If you unmount it and do it w/o -n, it should clear the error state. Perhaps it encountered an error for a file that got subsequently deleted, or something - not sure. -eric -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
