[arch-general] How do I _really_ fix the superblock?

2014-06-07 Thread Ralf Mardorf
Hi, I still need to comment out everything in fstab, excepted of / (it does include home) to boot Arch Linux, so at least I'm able to boot. Anyway, each time I boot, I get a message that the superblock's last write time was in the future, it always gets fixed and than always the / partition is

Re: [arch-general] How do I _really_ fix the superblock?

2014-06-07 Thread Jens Adam
Sat, 07 Jun 2014 13:36:08 +0200 Ralf Mardorf ralf.mard...@rocketmail.com: Could systemd be the culprit? Yes. https://bugs.archlinux.org/task/40706 --byte signature.asc Description: PGP signature

Re: [arch-general] How do I _really_ fix the superblock?

2014-06-07 Thread Ralf Mardorf
On Sat, 2014-06-07 at 13:50 +0200, Jens Adam wrote: Sat, 07 Jun 2014 13:36:08 +0200 Ralf Mardorf ralf.mard...@rocketmail.com: Could systemd be the culprit? Yes. https://bugs.archlinux.org/task/40706 Thank you and my apologize that I didn't check the bugs myself. I had the same

Re: [arch-general] How do I _really_ fix the superblock?

2014-06-07 Thread Doug Newgard
On 2014-06-07 06:57, Ralf Mardorf wrote: On Sat, 2014-06-07 at 13:50 +0200, Jens Adam wrote: Sat, 07 Jun 2014 13:36:08 +0200 Ralf Mardorf ralf.mard...@rocketmail.com: Could systemd be the culprit? Yes. https://bugs.archlinux.org/task/40706 Thank you and my apologize that I didn't check

Re: [arch-general] How do I _really_ fix the superblock?

2014-06-07 Thread Ralf Mardorf
On Sat, 2014-06-07 at 09:59 -0500, Doug Newgard wrote: The Beginner's Guide says: Warning: Using localtime may lead to several known and unfixable bugs. If you're going to do something non-standard that's known to cause problems, you have to expect things like this from time to time.

Re: [arch-general] How do I _really_ fix the superblock?

2014-06-07 Thread Bardur Arantsson
On 2014-06-07 17:46, Ralf Mardorf wrote: [--snip--] I suspect it's just the evil policy of those systemd folks, who want to teach everybody to follow there ways, as the only right ways. Please don't insinuate conspiracies without good evidence. IMO there's no valid reason not to chose

Re: [arch-general] How do I _really_ fix the superblock?

2014-06-07 Thread Ralf Mardorf
On Sat, 2014-06-07 at 17:54 +0200, Bardur Arantsson wrote: On 2014-06-07 17:46, Ralf Mardorf wrote: [--snip--] I suspect it's just the evil policy of those systemd folks, who want to teach everybody to follow there ways, as the only right ways. Please don't insinuate conspiracies

Re: [arch-general] How do I _really_ fix the superblock?

2014-06-07 Thread Leonid Isaev
On Sat, Jun 07, 2014 at 05:46:48PM +0200, Ralf Mardorf wrote: Date: Sat, 07 Jun 2014 17:46:48 +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

Re: [arch-general] How do I _really_ fix the superblock?

2014-06-07 Thread Doug Newgard
On 2014-06-07 11:05, Ralf Mardorf wrote: On Sat, 2014-06-07 at 17:54 +0200, Bardur Arantsson wrote: On 2014-06-07 17:46, Ralf Mardorf wrote: [--snip--] I suspect it's just the evil policy of those systemd folks, who want to teach everybody to follow there ways, as the only right ways.

Re: [arch-general] How do I _really_ fix the superblock?

2014-06-07 Thread Ralf Mardorf
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:

Re: [arch-general] How do I _really_ fix the superblock?

2014-06-07 Thread Ralf Mardorf
On Sat, 2014-06-07 at 11:14 -0500, Doug Newgard wrote: On 2014-06-07 11:05, Ralf Mardorf wrote: On Sat, 2014-06-07 at 17:54 +0200, Bardur Arantsson wrote: On 2014-06-07 17:46, Ralf Mardorf wrote: [--snip--] I suspect it's just the evil policy of those systemd folks, who want to

Re: [arch-general] How do I _really_ fix the superblock?

2014-06-07 Thread Alessandro Doro
On Sat, Jun 07, 2014 at 05:46:48PM +0200, Ralf Mardorf wrote: systemd, libsystemd and systemd-sysvcompat 213-6 from testing only solve the fstab issue, but they don't solve the superblock issue. - https://bugs.archlinux.org/task/40706 I never run into trouble before, because I use the local

Re: [arch-general] How do I _really_ fix the superblock?

2014-06-07 Thread Leonid Isaev
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

Re: [arch-general] How do I _really_ fix the superblock?

2014-06-07 Thread Ralf Mardorf
On Sat, 2014-06-07 at 18:36 +0200, Alessandro Doro wrote: It's not a new issue, maybe you're seeing it for the first time (localtime here), in coincidence with the forced fsck bug. Oops, sorry, not closed, I indeed missed something. My impression was, that the superblock issue does cause the

Re: [arch-general] How do I _really_ fix the superblock?

2014-06-07 Thread Ralf Mardorf
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

Re: [arch-general] How do I _really_ fix the superblock?

2014-06-07 Thread Leonid Isaev
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.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

Re: [arch-general] How do I _really_ fix the superblock?

2014-06-07 Thread Alessandro Doro
On Sat, Jun 07, 2014 at 06:44:21PM +0200, Ralf Mardorf wrote: On Sat, 2014-06-07 at 18:36 +0200, Alessandro Doro wrote: It's not a new issue, maybe you're seeing it for the first time (localtime here), in coincidence with the forced fsck bug. Oops, sorry, not closed, I indeed missed