[Bug 95896] Re: fsck forced after Feisty install: super node timestamp in the future

2007-09-06 Thread Jens
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. -- fsck forced after Feisty install: super node timestamp in the futu

[Bug 95896] Re: fsck forced after Feisty install: super node timestamp in the future

2007-05-07 Thread Philipp Wollermann
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. -- fsck forced after Feisty

[Bug 95896] Re: fsck forced after Feisty install: super node timestamp in the future

2007-05-06 Thread radev
Just installed Feisty Fawn final from DVD, both from graphical install and text mode. On first reboot described behavior happens. GMT+3 -- fsck forced after Feisty install: super node timestamp in the future https://bugs.launchpad.net/bugs/95896 You received this bug notification because you are

[Bug 95896] Re: fsck forced after Feisty install: super node timestamp in the future

2007-04-23 Thread ecir hana
happens here too, gmt+2 -- fsck forced after Feisty install: super node timestamp in the future https://bugs.launchpad.net/bugs/95896 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ub

[Bug 95896] Re: fsck forced after Feisty install: super node timestamp in the future

2007-04-23 Thread Michael Kofler
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 -- fsck forced after F

[Bug 95896] Re: fsck forced after Feisty install: super node timestamp in the future

2007-04-20 Thread Michael Kofler
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

[Bug 95896] Re: fsck forced after Feisty install: super node timestamp in the future

2007-03-25 Thread Ben Collins
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 (Ubunt