[Eisfair] fsck recommended - warum macht er es nicht selbst?

[Stefan Puschek]

Hallo Holger,

> 
> > aha:
> > 
> > barbrady # dmesg | grep fsck
> > [    6.362388] dracut: issuing e2fsck -a
> > /dev/disk/by-uuid/c48d26e8-607c-4e2a-8d0b-89b801ac45bd 
> [   10.360285]
> > EXT4-fs (sda1): warning: maximal mount count reached, running
> > e2fsck is recommended 
> [   10.481762] EXT4-fs (sda4): warning: maximal mount count
> > reached, running e2fsck is recommended barbrady 
> 
> # barbrady
> #> barbrady # dmesg | grep dracut
> > [    4.926317] dracut: eisfair-2.8.25
> > [    6.361915] dracut: Checking ext4:
> > /dev/disk/by-uuid/c48d26e8-607c-4e2a-8d0b-89b801ac45bd 
> > [    6.362388] dracut: issuing e2fsck -a
> > /dev/disk/by-uuid/c48d26e8-607c-4e2a-8d0b-89b801ac45bd 
> [    6.450439] dracut: 
> /dev/disk/by-uuid/c48d26e8-607c-4e2a-8d0b-89b801ac45bd: clean,
> > 58523/1040384 files, 658721/4132864 blocks 
> 
> brady #
> > 
> > hat er den Check nun gemacht oder nicht?
> 
> da steht doch clean

das sehe ich, aber:
barbrady # cat /etc/fstab
UUID=c48d26e8-607c-4e2a-8d0b-89b801ac45bd / ext4
defaults,errors=remount-ro 0 1
das ist sda3


UUID=b16f5a30-dc78-4c23-a2fa-f3ec1218fd12 /boot ext4
defaults,errors=remount-ro 0 1
das ist sda1


UUID=c0d4d4f4-4b14-4d3f-a982-5855d4699aa8 none swap sw 0 0
das ist sda2


UUID=a1ede65c-f351-4f73-a427-5f5e2eac5b76 /home ext4
defaults,errors=remount-ro 0 1 
das ist sda4


dmesg
...
[   10.355663] EXT4-fs (sda3): re-mounted. Opts: errors=remount-ro.
Quota mode: none. [   10.474719] EXT4-fs (sda1): warning: maximal mount
count reached, running e2fsck is recommended [   10.483936] EXT4-fs
(sda1): mounted filesystem with ordered data mode. Opts:
errors=remount-ro. Quota mode: none. [   10.483990] ext4 filesystem
being mounted at /boot supports timestamps until 2038 (0x7fffffff) [
10.547402] EXT4-fs (sda4): warning: maximal mount count reached,
running e2fsck is recommended [   10.667558] EXT4-fs (sda4): mounted
filesystem with ordered data mode. Opts: errors=remount-ro. Quota mode:
none.


warum macht er den check nicht bei sda1 und sda4?
barbrady # tune2fs -l /dev/sda1|grep count
Inode count:              32768
Block count:              131072
Reserved block count:     6552
Mount count:              43
Maximum mount count:      20
barbrady # 
barbrady # tune2fs -l /dev/sda4|grep count
Inode count:              120922112
Block count:              483685888
Reserved block count:     24184291
Mount count:              43
Maximum mount count:      20
barbrady # 

Habe ich hier falsche Erwartungen?

Ich will nicht meckern - ich wills nur wissen :)

Groetjes
Stefan