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

Re: /boot partition changes when it should not



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Mario 'BitKoenig' Holbe wrote:
> Clive McBarton <clivemcbarton@web.de> wrote:
>> and while the system is turned off. The "online to offline" comparison
>> works fine, whereas the "offline to online" does not always work, hence
> 
> What exactly does "not always" mean?

That's what I tried to explain in the paragraph before (before what you
quoted):

"More precisely: You never know if any
checksums taken on a running system are reported correctly. But: If you
take an online system (powered up), take checksums of important files or
partitions, and they are the same after the system later becomes offline
(powered down), then they were reported correctly to begin with. Whereas
if they were correct before running it and are then are reported correct
while the system is running, it does not tell you anything."

> Maybe it's just the periodic fsck which changes the mount count?
> Check your fstab for the last field (fs_passno). Set either this to 0 to
> disable periodic checks and/or use tune2fs -c and tune2fs -i to disable
> periodic full checks (not recommended, btw.).

Good idea. I now turned off the fstab checks and also both entries with
tune2fs. Since nothing on the /boot partition is allowed to change, fsck
serves no purpose any longer. More precisely, the change detector must
notice anything anyway that fsck would see.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkuYdbgACgkQ+VSRxYk44094qQCaA6dGZwOgm24xyMnIz+rLMA2I
99MAn2qQrUoKS520k97rDsb45QR63sfR
=Logz
-----END PGP SIGNATURE-----


Reply to: