linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephan Kulow <coolo@suse.de>
To: Theodore Tso <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org, Scott James Remnant <scott@canonical.com>
Subject: Re: buggy_init_scritps and e2fsprogs 1.41.9
Date: Thu, 10 Sep 2009 22:57:54 +0200	[thread overview]
Message-ID: <200909102257.54889.coolo@suse.de> (raw)
In-Reply-To: <20090910202927.GK23700@mit.edu>

On Thursday 10 September 2009 22:29:27 Theodore Tso wrote:
> 
> > I don't want to set buggy_init_scripts for openSUSE as the init
> > scripts are not buggy, but a live cd is a live cd and has no idea
> > what the timezone of the system is configured to and even a ro
> > mount will destroy your file system ;(
> 
> Well, you're over-dramatizing things; it doesn't destroy your
> filesystem --- it just forces an unnnecessary fsck.  And it only does
> this if the system had been uncleanly shutdown before the the boot.
> 
Yes, it doesn't destroy your file system but it forces you to do a manual
fsck and no, there is no need for a unclean shutdown, it will always happen.

The work flow is as such:
- boot into live cd, live cd thinks system is UTC, mounts sda1 (ro) 
  at 9am, umounts cleanly, updates mount time to 11am (hardware clock)
- boot into real system, time is set to CEST and hardware clock is read
  as 9am. fsck will say the file has uncorrectable errors and abort.

This does _not_ happen with 1.14.8 as PR_0_FUTURE_SB_LAST_MOUNT
contained PR_PREEN_OK and that makes it continue.
Now 1.14.9 does preenhalt on the two hour difference of mount time  
even as the problem is just as harmless - and it will not appear
on distributions with buggy init scripts.

Your kernel patch makes sense, but it won't change the problem: because the 
problem is mtime not wtime.

Greetings, Stephan

  reply	other threads:[~2009-09-10 20:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-10 12:55 buggy_init_scritps and e2fsprogs 1.41.9 Stephan Kulow
2009-09-10 13:03 ` Stephan Kulow
2009-09-10 13:11   ` Stephan Kulow
2009-09-10 20:29 ` Theodore Tso
2009-09-10 20:57   ` Stephan Kulow [this message]
2009-09-11  0:55     ` Theodore Tso
2009-09-11 10:38       ` Stephan Kulow
2009-09-10 21:32   ` Theodore Tso

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200909102257.54889.coolo@suse.de \
    --to=coolo@suse.de \
    --cc=linux-ext4@vger.kernel.org \
    --cc=scott@canonical.com \
    --cc=tytso@mit.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).