[SOLVED] Debian doesn't fsck non-root partitions at boot

the98 · 12-14-2014, 10:31 AM

I've noticed that Debian is not running fsck on partitions that are not /

So I wonder if this is related to the number "2" defined in the "pass" section of fstab. Here is my fstab.

Code:

# /etc/fstab: static file system information.
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>

/dev/sr0     /media/cdrom0   udf,iso9660 user,noauto     0       0
/dev/fd0        /media/floppy0  auto  rw,user,noauto,sync   0       0

#/dev/sdA------------------------------------------------------------------------------
proc            /proc           proc    defaults        0       0
/dev/sda1       /               ext3    defaults,atime,errors=remount-ro 0       1
/dev/sda2       none            swap    sw              0       0
/dev/sda3      /media/Musica        ext4    defaults,atime,errors=remount-ro    0   2 

#/dev/sdB------------------------------------------------------------------------------
/dev/sdb2      /media/Documentos    ext4    defaults,atime,errors=remount-ro    0   2
/dev/sdb1      /media/Shared        ext4    defaults,atime,errors=remount-ro    0   2 

#RED-LAPTOP----------------------------------------------------------------------------
/home    /.export/home   none    bind  0  0
/media/Documentos    /.export/Documentos   none    bind  0  0
/media/Musica    /.export/Musica   none    bind  0  0
/media/Shared    /.export/Shared   none    bind  0  0
/tmp    /.export/tmp100   none    bind  0  0

But, according to Debian Wiki, this is the way to define non-root partitions:

Quote:

<pass> fsck reads the <pass> number and determines in which order the file systems should be checked. Possible entries are 0, 1, and 2. The root file system should have the highest priority, 1, all other file systems you want to have checked should get a 2. File systems with a <pass> value 0 will not be checked by the fsck utility.

https://wiki.debian.org/fstab

Any ideas on what I should check?

Every non-root partition has not being checked since 4-3-2013, which makes me think there was some update or something that created this issue.

Code:

tune2fs -l /dev/sda3 | grep "Last checked"
Last checked:             Wed Apr  3 19:24:02 2013

I don't think this is systemd related, because I think back in 2013, systemd was not installed.

I'm under Debian Sid, by the way.

Any way, any advice would be appreciated. Thanks!

jailbait · 12-14-2014, 11:35 AM

There is a maximum mount count in the file system metadata. The system only does a fsck on a file system when it has been mounted the maximum number of times without a fsck. You can list the maximum mount count and the current mount count with tune2fs. A maximum mount count of -1 means to never run fsck when mounting the file system.

The only other time that fsck is run at boot is when the system shuts down without doing a umount on the file system.

The pass number is unrelated to when fsck is run. The pass number is used to indicate which mount points are found on other file systems. Therefore the secondary mount points cannot be mounted until the primary file system has been mounted. The pass number is not limited to a maximum of 2. I use 3 passes and I have answered questions here on linuxquestions where the solution to the problem was to have 3 or more passes in fstab.

------------------------
Steve Stites

the98 · 12-14-2014, 02:49 PM

Thank you.

You're right, I checked with tune2fs, and found out the Maximum Count is set to -1. I don't think I've done this, so maybe Debian has done this on some update.

jailbait · 12-14-2014, 04:38 PM

Quote:

Originally Posted by the98

Thank you.

You're right, I checked with tune2fs, and found out the Maximum Count is set to -1. I don't think I've done this, so maybe Debian has done this on some update.

Most likely it was done by the program that formatted the filesystem.

-------------------
Steve Stites

syg00 · 12-14-2014, 07:43 PM

It is now the default (i.e. upstream) behaviour - see this redhat bugzilla; note comment 4.