On Sat, Jun 07, 2014 at 06:23:49PM +0200, Ralf Mardorf wrote: > Date: Sat, 07 Jun 2014 18:23:49 +0200 > From: Ralf Mardorf <ralf.mard...@rocketmail.com> > To: arch-general@archlinux.org > Subject: Re: [arch-general] How do I _really_ fix the superblock? > X-Mailer: Evolution 3.12.2 > > On Sat, 2014-06-07 at 12:12 -0400, Leonid Isaev wrote: > > your clock is not correct apparently. > > The clock provides the correct localtime. There's no issue caused by the > clock. The issue only appears for Arch Linux with systemd from the > repositories > version 212-3. It worked before: > > [rocketmouse@archlinux ~]$ grep systemd /var/log/pacman.log > [snip] > [2013-02-17 02:59] installed systemd (197-4) > [snip] > [2014-06-04 08:34] [PACMAN] upgraded libsystemd (212-3 -> 213-5) > [2014-06-04 08:34] [PACMAN] upgraded systemd (212-3 -> 213-5) > [2014-06-04 08:34] [PACMAN] upgraded systemd-sysvcompat (212-3 -> 213-5) > [snip] > [2014-06-07 17:19] [PACMAN] Running 'pacman -U > systemd-213-6-x86_64.pkg.tar.xz libsystemd-213-6-x86_64.pkg.tar.xz > systemd-sysvcompat-213-6-x86_64.pkg.tar.xz' > [2014-06-07 17:19] [PACMAN] upgraded libsystemd (213-5 -> 213-6) > [2014-06-07 17:19] [PACMAN] upgraded systemd (213-5 -> 213-6) > [2014-06-07 17:19] [PACMAN] upgraded systemd-sysvcompat (213-5 -> 213-6) > > And it always worked without a problem for all other Linux and FreeBSD > installs on my machines.
Just out of curiosity, when exactly do you see the fsck warning: at each
reboot, or when booting after some downtime? Also, how do you syncronize time:
ntpd/chrony/timesyncd?
>
> If it's a new policy, then there's no reason to discuss this on the
> mailing list.
>
There is no policy, just common sense...
--
Leonid Isaev
GPG fingerprints: DA92 034D B4A8 EC51 7EA6 20DF 9291 EE8A 043C B8C4
C0DF 20D0 C075 C3F1 E1BE 775A A7AE F6CB 164B 5A6D
pgpQcZy6VVvrX.pgp
Description: PGP signature
