Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #175176

Re: forcefsck inconsistency

From Michael Biebl <biebl@debian.org>
Newsgroups linux.debian.user
Subject Re: forcefsck inconsistency
Date 2016-11-28 18:10 +0100
Message-ID <sIxBf-4SJ-19@gated-at.bofh.it> (permalink)
References (3 earlier) <sGL5E-rk-19@gated-at.bofh.it> <sHHt0-4DN-9@gated-at.bofh.it> <sIu0G-2yY-25@gated-at.bofh.it> <sIutI-2IY-21@gated-at.bofh.it> <sIuWJ-3cd-3@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


[Multipart message — attachments visible in raw view] - view raw

Am 28.11.2016 um 15:10 schrieb Pierre Frenkiel:
> On Mon, 28 Nov 2016, Michael Biebl wrote:

>  thank you for this usefull information, but some inconsistency remains:
> 
> in /run/initramfs/fsck.log, I find:
> 
>      Log of fsck -C -a -V -t ext4 /dev/sda2
>      Sat Nov 26 06:53:12 2016
> 
>      fsck from util-linux 2.25.2
>      [/sbin/fsck.ext4 (1) -- /dev/sda2] fsck.ext4 -a -C0 /dev/sda2
>      /dev/sda2: clean, 424229/1679360 files, 3245606/6704384 blocks
> 
>      Sat Nov 26 06:53:13 2016
>      ----------------
> 
> and tune2fs -l /dev/sda2 gives:
> 
>     Last checked:             Fri Nov 25 22:45:38 2016
> 
> and on an other PC, the difference is much bigger (24/10/2016 and
> 17/11/2016)
> 
> as for fsck-root, it is empty on both.

Oh, this is quite simple to explain.
If your file system is clean, fsck will simply do nothing.

The "Last checked" attribute is only reset, if fsck is actually run due to
1/ unclean file system
2/ forced fsck (fsck.mode=force on the kernel command line)
3/ max mount count or check interval reached.



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

forcefsck inconsistency Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2016-11-22 20:00 +0100
  Re: forcefsck inconsistency David Wright <deblis@lionunicorn.co.uk> - 2016-11-22 20:50 +0100
    Re: forcefsck inconsistency Pierre Frenkiel <pierre.frenkiel@gmx.com> - 2016-11-22 23:50 +0100
      Re: forcefsck inconsistency David Wright <deblis@lionunicorn.co.uk> - 2016-11-23 20:10 +0100
        Re: forcefsck inconsistency Pierre Frenkiel <pierre.frenkiel@gmx.com> - 2016-11-26 10:30 +0100
          Re: forcefsck inconsistency Richard Hector <richard@walnut.gen.nz> - 2016-11-28 14:20 +0100
            Re: forcefsck inconsistency Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2016-11-28 14:30 +0100
            Re: forcefsck inconsistency Michael Biebl <biebl@debian.org> - 2016-11-28 14:50 +0100
              Re: forcefsck inconsistency Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2016-11-28 15:20 +0100
                Re: forcefsck inconsistency Michael Biebl <biebl@debian.org> - 2016-11-28 18:10 +0100
                Re: forcefsck inconsistency Pierre Frenkiel <pierre.frenkiel@gmx.com> - 2016-11-28 20:00 +0100
                Re: forcefsck inconsistency Michael Biebl <biebl@debian.org> - 2016-11-29 00:20 +0100
                Re: forcefsck inconsistency Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2016-11-29 08:50 +0100
                Re: forcefsck inconsistency Michael Biebl <biebl@debian.org> - 2016-11-29 12:40 +0100
                Re: forcefsck inconsistency Pierre Frenkiel <pierre.frenkiel@gmx.com> - 2016-11-29 13:50 +0100

csiph-web