Ubuntu
linux-meta package

fsck forced after Feisty install: super node timestamp in the future

Bug #95896 reported by Mikko Ohtamaa
14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux-meta (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I installed Feisty Fawn to my HP nx9420 laptop. I created ext3 root filesytem to /dev/sda7 partition. I set timezone to GMT+2 (Helsinki).

During the first boot, the boot loader complains that "super node timestamp is in the future" or similiar message (didn't write down the exact message) and fsck is forced. After this, the computer reboot.

1) This is unnecessary

2) This confuses non-tech-sawy users

Revision history for this message
Ben Collins (ben-collins) wrote :

The filesystems are created with rules on how often to force a fsck. This scenario triggered it. I doubt it's a common one. We don't want to change these rules for corner cases.

Not to mention, even if this was considered a bug, it's not the kernel that does this.

Changed in linux-meta:
status: Unconfirmed → Rejected
Revision history for this message
Michael Kofler (michael-kofler) wrote :

I can confirm this 'not a bug' (is it a feature, then?) with Feisty final alternate CD i386

I had the same problem with Feisty beta desktop CD, will retest with final as soon as I finish the download

timezone GMT+1 (Berlin)

I would guess this bug is triggered on all installations with a timezone GMT+n>0; even if the U.S. are safe from this bug, I would still call this a common scenario ...

Revision history for this message
Michael Kofler (michael-kofler) wrote :

happens also with Feisty final desktop

however, I am no longer sure whether this is a timezone related problem; I installed Feisty, then had to go away and did the first reboot three days later; still the node timestamp was in the future, so it cannot be the GMT+n timestep

Revision history for this message
ecir hana (ecir-hana) wrote :

happens here too, gmt+2

Revision history for this message
radev (radev) wrote :

Just installed Feisty Fawn final from DVD, both from graphical install and text mode.
On first reboot described behavior happens. GMT+3

Revision history for this message
Philipp Wollermann (philipp) wrote :

Happens here reproducible at least in VMware install. Was also using ext3 as filesystem for /. The message says that the superblock was modified 49400 days in the future, it checks the filesystem, finds some evil error and reboots. Then it restarts with a clean mount.

Revision history for this message
Jens (jens-launchpad-net) wrote : [gutsy] fsck forced after Feisty install: super node timestamp in the future

Hello,

this still happens on a Gutsy installation, using ext3, directly after installation. My guess is also that the change in time zone or otherwise adjusting the computer clock does this.

IMHO: this is a grave bug, since all users east of GMT+0 (Greenwich, London) are affected by this and it makes Ubuntu look "broken" on first sight. Not very trustworthy, if the first thing a new OS needs to do is repair itself.

Jens

Revision history for this message
Jens (jens-launchpad-net) wrote :

IMHO: this is a grave bug, since all users east of GMT+0 (Greenwich, London) are affected by this and it makes Ubuntu look "broken" on first sight. Not very trustworthy, if the first thing a new OS needs to do is repair itself.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.