On Sat, Jun 07, 2014 at 06:49:58PM +0200, Ralf Mardorf wrote:
Date: Sat, 07 Jun 2014 18:49:58 +0200 From: Ralf Mardorf <ralf.mardorf@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:43 -0400, Leonid Isaev wrote:
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?
I see the warning with each startup, it doesn't matter if I reboot or if I boot after a long downtime. The clock is ok. I sync manually
[rocketmouse@archlinux ~]$ cat /usr/local/bin/tool #!/bin/bash
# /usr/local/bin/tool
case $1 in [snip] ntp) ntpdate ntp.favey.ch hwclock --set --date "$(date)";; [snip]
Just an advice: replace this with a continuously tunning ntpd or at least with ntpd -q.
The warning about the wrong superblock time isn't an issue, the problem is that with each startup the / partition is checked. I thought this is caused by the wrong superblock time, but IIUC it's another bug.
That's actually interesting. Whether / will be fsck'ed or not depends on your mkinitcpio hooks (fsck) and kernel cmdline. What are them? Do you have "ro" in the cmdline? -- Leonid Isaev GPG fingerprints: DA92 034D B4A8 EC51 7EA6 20DF 9291 EE8A 043C B8C4 C0DF 20D0 C075 C3F1 E1BE 775A A7AE F6CB 164B 5A6D