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

Groups > linux.debian.user > #183007

Re: Superblock last write time is in the future.

Show key headers only | View raw

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

On Mon, Jul 03, 2017 at 08:25:58AM -0300, Wellington Terumi Uemura wrote:
> Looks like people can't make up their minds, /etc/adjtime is missing
> from initramfs.
> 
> root@Dragon:/boot# lsinitramfs /boot/initrd.img-4.9.0-3-amd64|grep etc
> etc
> etc/ld.so.cache
> etc/mtab
> etc/ld.so.conf.d
> etc/ld.so.conf.d/zz_i386-biarch-compat.conf
> etc/ld.so.conf.d/libc.conf
> etc/ld.so.conf.d/x86_64-linux-gnu.conf
> etc/udev
> etc/udev/udev.conf
> etc/ld.so.conf
> etc/fstab
> etc/modprobe.d
> etc/modprobe.d/cx23885.conf
> etc/modprobe.d/amd64-microcode-blacklist.conf
> etc/modprobe.d/sp5100_tco-blacklist.conf
> 
> And people say that this is the problem.
> https://bugzilla.redhat.com/show_bug.cgi?id=1198761
> 
> Looks like all we need to do is to add /etc/adjtime back to initramfs.

Hmm, yes -- initramfs and the "up and running" OS should agree on what
corrections to apply to the time read from the hwclock; if not, it
sounds plausible that initramfs (who is mounting root, and thus checking
the superblock) has a different notion of time than the OS, who has
synced out the superblock on last shutdown.

I can't work out the details, but what you say makes a lot of sense.

Cheers
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAllaMGEACgkQBcgs9XrR2kbeFwCfXntl7ShEl0ea/YVsZklT+f8T
iOgAniBpUE6yABvzBoYf0kD0bL+j1rxE
=ngfH
-----END PGP SIGNATURE-----

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

Thread

Superblock last write time is in the future. Wellington Terumi Uemura <wellingtonuemura@gmail.com> - 2017-06-21 07:50 +0200
  Re: Superblock last write time is in the future. Michael Biebl <biebl@debian.org> - 2017-06-21 12:00 +0200
    Re: Superblock last write time is in the future. Wellington Terumi Uemura <wellingtonuemura@gmail.com> - 2017-07-02 18:00 +0200
      Re: Superblock last write time is in the future. Michael Biebl <biebl@debian.org> - 2017-07-02 19:30 +0200
        Re: Superblock last write time is in the future. Wellington Terumi Uemura <wellingtonuemura@gmail.com> - 2017-07-02 21:30 +0200
      Re: Superblock last write time is in the future. Siard <shiems146@kpnplanet.nl> - 2017-07-02 22:40 +0200
        Re: Superblock last write time is in the future. Wellington Terumi Uemura <wellingtonuemura@gmail.com> - 2017-07-02 23:10 +0200
          Re: Superblock last write time is in the future. <tomas@tuxteam.de> - 2017-07-03 09:40 +0200
            Re: Superblock last write time is in the future. Wellington Terumi Uemura <wellingtonuemura@gmail.com> - 2017-07-03 13:30 +0200
              Re: Superblock last write time is in the future. <tomas@tuxteam.de> - 2017-07-03 14:00 +0200
                Re: Superblock last write time is in the future. Cindy-Sue Causey <butterflybytes@gmail.com> - 2017-07-03 15:30 +0200
                Re: Superblock last write time is in the future. David Wright <deblis@lionunicorn.co.uk> - 2017-07-03 17:30 +0200
            Re: Superblock last write time is in the future. David Wright <deblis@lionunicorn.co.uk> - 2017-07-03 17:10 +0200
              Re: Superblock last write time is in the future. Wellington Terumi Uemura <wellingtonuemura@gmail.com> - 2017-07-03 18:10 +0200
                Re: Superblock last write time is in the future. David Wright <deblis@lionunicorn.co.uk> - 2017-07-03 21:50 +0200
                Re: Superblock last write time is in the future. Wellington Terumi Uemura <wellingtonuemura@gmail.com> - 2017-07-03 22:10 +0200
                Re: Superblock last write time is in the future. Nicolas George <george@nsup.org> - 2017-07-03 22:20 +0200
                Re: Superblock last write time is in the future. David Wright <deblis@lionunicorn.co.uk> - 2017-07-04 05:50 +0200
              Re: Superblock last write time is in the future. Gene Heskett <gheskett@shentel.net> - 2017-07-03 19:00 +0200
          Re: Superblock last write time is in the future. Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-07-03 21:10 +0200
            Re: Superblock last write time is in the future. Wellington Terumi Uemura <wellingtonuemura@gmail.com> - 2017-07-03 21:50 +0200
            Re: Superblock last write time is in the future. Felix Miata <mrmazda@earthlink.net> - 2017-07-03 23:40 +0200
              Re: Superblock last write time is in the future. Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-07-04 21:30 +0200
                Re: Superblock last write time is in the future. Felix Miata <mrmazda@earthlink.net> - 2017-07-04 22:20 +0200
                Re: Superblock last write time is in the future. Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-07-04 22:50 +0200

csiph-web