Arch Linux

freedomd1v3

Member

Registered: 2020-12-01

Posts: 12

[Solved] What "Maximum mount count: -1" from dumpe2fs stands for?

According to ArchWiki:

Note that 1 would make it scan at every boot, while 0 would stop scanning altogether.

But what -1 stands for then? Is it the default? If so, what is the default's value?

Thanks.

Last edited by freedomd1v3 (2020-12-07 09:07:51)

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,361

Re: [Solved] What "Maximum mount count: -1" from dumpe2fs stands for?

       -c max-mount-counts
              Adjust the number of mounts after which the filesystem will be checked by  e2fsck(8).   If  max-mount-
              counts  is 0 or -1, the number of times the filesystem is mounted will be disregarded by e2fsck(8) and
              the kernel.

              Staggering the mount-counts at which filesystems are forcibly checked will avoid all filesystems being
              checked at one time when using journaled filesystems.

              Mount-count-dependent checking is disabled by default to avoid unanticipated long reboots while e2fsck
              does its work.  However, you may wish to consider the consequences of disabling  mount-count-dependent
              checking  entirely.   Bad  disk drives, cables, memory, and kernel bugs could all corrupt a filesystem
              without marking the filesystem dirty or in error.  If you are using  journaling  on  your  filesystem,
              your  filesystem  will  never be marked dirty, so it will not normally be checked.  A filesystem error
              detected by the kernel will still force an fsck on the next reboot, but it may already be too late  to
              prevent data loss at that point.

              See also the -i option for time-dependent checking.

       -C mount-count
              Set  the  number  of  times  the filesystem has been mounted.  If set to a greater value than the max-
              mount-counts parameter set by the -c option, e2fsck(8) will check the filesystem at the next reboot.

Read it's equivalent.

Last edited by V1del (2020-12-07 08:59:57)

freedomd1v3

Member

Registered: 2020-12-01

Posts: 12

Re: [Solved] What "Maximum mount count: -1" from dumpe2fs stands for?

       -c max-mount-counts
              Adjust the number of mounts after which the filesystem will be checked by  e2fsck(8).   If  max-mount-
              counts  is 0 or -1, the number of times the filesystem is mounted will be disregarded by e2fsck(8) and
              the kernel.

              Staggering the mount-counts at which filesystems are forcibly checked will avoid all filesystems being
              checked at one time when using journaled filesystems.

              Mount-count-dependent checking is disabled by default to avoid unanticipated long reboots while e2fsck
              does its work.  However, you may wish to consider the consequences of disabling  mount-count-dependent
              checking  entirely.   Bad  disk drives, cables, memory, and kernel bugs could all corrupt a filesystem
              without marking the filesystem dirty or in error.  If you are using  journaling  on  your  filesystem,
              your  filesystem  will  never be marked dirty, so it will not normally be checked.  A filesystem error
              detected by the kernel will still force an fsck on the next reboot, but it may already be too late  to
              prevent data loss at that point.

              See also the -i option for time-dependent checking.

       -C mount-count
              Set  the  number  of  times  the filesystem has been mounted.  If set to a greater value than the max-
              mount-counts parameter set by the -c option, e2fsck(8) will check the filesystem at the next reboot.

Read it's equivalent.

Ok, thanks, solved.