[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: forcefsck inconsistency



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?

Attachment: signature.asc
Description: OpenPGP digital signature


Reply to: