To find out whether a filesystem check is scheduled for the next boot. Use this command: “dumpe2fs -h /dev/disk”.
Fsck will run if mount count is equal or greater than maximum mount count, or if “next check after” is passed.
srv025:~ # dumpe2fs -h /dev/sda2
dumpe2fs 1.41.9 (22-Aug-2009)
Filesystem volume name:
Last mounted on:
Filesystem UUID: 076cd21e-aeca-4547-9632-3020f8ef414c
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery sparse_super large_file
Filesystem flags: signed_directory_hash
Default mount options: (none)
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 3014656
Block count: 12056832
Reserved block count: 602671
Free blocks: 4111462
Free inodes: 2786894
First block: 0
Block size: 4096
Fragment size: 4096
Reserved GDT blocks: 1021
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 8192
Inode blocks per group: 512
Filesystem created: Mon Feb 27 14:13:38 2017
Last mount time: Tue May 1 10:02:39 2018
Last write time: Tue May 1 10:02:39 2018
Mount count: 21
Maximum mount count: 39
Last checked: Tue Apr 17 11:54:40 2018
Check interval: 15552000 (6 months)
Next check after: Sun Oct 14 11:54:40 2018
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Required extra isize: 28
Desired extra isize: 28
Journal inode: 8
Default directory hash: half_md4
Directory Hash Seed: 3898b141-f1a6-470c-a491-f0c0777875e5
Journal backup: inode blocks
Journal size: 128M
srv025:~ #