** Changed in: e2fsprogs (Debian)
Status: Won't Fix => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/43239
Title:
fsck should check against a timestamp "49710 days" old
Yes, this can be different again now that the hwclock setting is done by
a udev rule instead of an init script. Caracuri, can you please file a
new bug, using "ubuntu-bug util-linux"?
--
fsck should check against a timestamp "49710 days" old
https://bugs.launchpad.net/bugs/43239
You received this
also i have this problem with:
Linux notebook 2.6.31-9-generic #29-Ubuntu SMP Sun Aug 30 17:39:23 UTC 2009
i686 GNU/Linux
Ubuntu Karmic Koala
--
fsck should check against a timestamp "49710 days" old
https://bugs.launchpad.net/bugs/43239
You received this bug notification because you are a mem
** Description changed:
If the system clock has been misadjusted while fsck last run, fsck
reports on next boot that the partition "has gone 49710 days without
being checked, check forced". Happens to me in Ubuntu after I do an
occasional boot to a parallel partition if fsck gets run there
** Tags added: iso-testing
--
fsck should check against a timestamp "49710 days" old
https://bugs.launchpad.net/bugs/43239
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://l
** Changed in: e2fsprogs (Debian)
Status: Confirmed => Won't Fix
--
fsck should check against a timestamp "49710 days" old
https://bugs.launchpad.net/bugs/43239
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailin
** Changed in: e2fsprogs (Debian)
Status: Unknown => Confirmed
** Changed in: util-linux (Debian)
Status: Unknown => Fix Released
--
fsck should check against a timestamp "49710 days" old
https://bugs.launchpad.net/bugs/43239
You received this bug notification because you are a mem
In Gutsy, hwclock is started at S11, which in Ubuntu is after S10udev
and before S20checkroot.sh, so this should be fine now. Please reopen if
you can reproduce with Gutsy.
WRT to the question of fsck'ing if the timestamp is in the future: Then
you know the clock is wrong, and you can not trust it
Thank you again for the clarification. (And yes, you are correct in
stating that the time it takes to run a filesystem check is what users
will complain about.)
I am still unsure whether forcing a filesystem check when the timestamp
is in the future is the desired action. As it is not my decision
Thanks Theodore, that sounds good.
** Changed in: util-linux (Ubuntu)
Sourcepackagename: sysvinit => util-linux
** Also affects: util-linux (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=342887
Importance: Unknown
Status: Unknown
--
fsck should check against a timest
Well, the problem is fundamentally more about the initscripts and util-
linux than it is about e2fsprogs. The message printed by e2fsprogs
will change, so that it says the time is in the future, as opposed to
49710 days. But the root cause of the bug really is the fact that the
system clock is
We have to keep one Ubuntu task open as long as the bug is not fixed in
Ubuntu. Note that the Status of the (Ubuntu) tasks reflects the status
in Ubuntu and not upstream. You can open (upstream) tasks which can have
independent status.
If the e2fsprogs issue is fixed upstream, and we just wait for
** Also affects: e2fsprogs (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=343645
Importance: Unknown
Status: Unknown
--
fsck should check against a timestamp "49710 days" old
https://bugs.launchpad.net/bugs/43239
You received this bug notification because you are a mem
Thank you for looking into this.
"In the latest versions of e2fsprogs, e2fsck will print a messaging that
the clock is insane, and then check the filesystem since it could also
be the case that the clock is insane."
If I understand correctly, this should be sufficient to consider the
originally r
I started looking further on this issue, and it looks like it has been
fixed in util-linux by making /etc/localtime a file, and by making sure
the timezone is set correctly at boot time. See these debian bug
reports:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=343645
http://bugs.debian.org/c
The fundamental bug here is in the init scripts. E2fsck assumes that
the system time is correct. Unfortunately, if you have the system time
set to tick localtime, instead of GMT, the Debian/Ubuntu boot scripts do
not adjust for the fact that the hardware clock is not ticking UTC until
after chec
Update: when you boot Debian Etch for the first time, after installing
it into /dev/sda3 on a system with Windows in /dev/sda1, you also get
this fsck error. I've installed Etch numerous times on other (Linux-
only) systems without any issues whatsoever.
--
fsck should check against a timestamp "
This happened to me too, during the installation of ubuntu 7.04 final.
On the first reboot after installation, fsck checked all my partitions
(quite annoying in itself). Fsck reported "Superblock last mount time is
in the future" on all partitions, and on /dev/sda9 I got the "has gone
49710 days wi
Same here, same message and amount of days (it's /dev/sda6 in my case
because that's where my root partition is). I'm dual-booting with XP and
Vista but hadn't booted these since wiping Ubuntu 6.10.
--
fsck should check against a timestamp "49710 days" old
https://bugs.launchpad.net/bugs/43239
Yo
Same here. GMT+2 time zone and Kubuntu 7.04 daily build 20070417. In my
case it (fsck?) claimed that some time stamp was in the future, did some
tweaking, rebooted computer and kubuntu started well.
--
fsck should check against a timestamp "49710 days" old
https://bugs.launchpad.net/bugs/43239
Yo
Happened to me also (Kubuntu 7.04 daily build 20070417). During the
first boot fsck checked root partition and told me that it had found
some errors and then rebooted my machine.
I had set my system to GMT+2 time zone.
--
fsck should check against a timestamp "49710 days" old
https://bugs.launch
It seems the issue is that the installer is not correct. You set the
time zone to London and you get BST+1, when really it should be GMT+1 I
believe.
BST in the installer seems to be = GMT + 1 + 1
--
fsck should check against a timestamp "49710 days" old
https://bugs.launchpad.net/bugs/43239
You
I get this also when installing the 7.04 betas and the RC.
My system is set to the current time here in the UK. The live CD is booting -1
hour and during installation
it comes to current time. Upon reboot the system is forcing fsck because the
timestamp for the last
mount is in the past.
Includ
This happened to me also, after installing ubuntu 7.04 beta in an
already partitioned hard drive (/dev/sda9, local time Rome/Italy).
--
fsck should check against a timestamp "49710 days" old
https://bugs.launchpad.net/bugs/43239
You received this bug notification because you are a member of Ubunt
The problem still exists using Kubuntu 7.04 (Feisty Fawn) Beta x86
Desktop CD.
BIOS time/CMOS time is set to local time ("Berlin/Germany"). After
booting the Desktop CD (the clock shows the correct local time) I
started the Installation, chose Berlin/Germany in "step 2 of 6" and re-
formatted the
25 matches
Mail list logo
