[Bug 43239] Re: fsck should check against a timestamp "49710 days" old
** 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/43239/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 43239] Re: 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 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 43239] Re: fsck should check against a timestamp "49710 days" old
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 member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 43239] Re: fsck should check against a timestamp "49710 days" old
** 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. This is clearly nonsense. A quick google of "fsck 49710" gives out numerous examples, revealing inter alia that 49710 days is close to 2^32 seconds, and gives a clear indication that fsck simply isn't equipped to deal with a misconfigured system clock. In such a case fsck should only run if the filesystem was actually marked "dirty", i.e. not just because of the old timestamp. In addition, fsck probably could fix the timestamp. - - The problem is annoying. It often occurs for me when I try to debug various system configuration issues (mainly X). Sometimes the system hangs, leading to a hard boot, leading to fsck, often leading to the further aggravation of unnecessary fsck checks due to a 136-year old timestamp. + The problem is annoying. It often occurs for me when I try to debug + various system configuration issues (mainly X). Sometimes the system + hangs, leading to a hard boot, leading to fsck, often leading to the + further aggravation of unnecessary fsck checks due to a 136-year old + timestamp. -- 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 43239] Re: fsck should check against a timestamp "49710 days" old
** 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 43239] Re: fsck should check against a timestamp "49710 days" old
** 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 mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 43239] Re: fsck should check against a timestamp "49710 days" old
** 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 member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 43239] Re: fsck should check against a timestamp "49710 days" old
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, and you should fsck just to be sure. ** Changed in: util-linux (Ubuntu) Status: Confirmed => 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 member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 43239] Re: fsck should check against a timestamp "49710 days" old
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 to make, I must trust your judgment in whether an unwarranted fsck can (could) be avoided in such a case. -- 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 43239] Re: fsck should check against a timestamp "49710 days" old
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 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 43239] Re: fsck should check against a timestamp "49710 days" old
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 not set correctly at the time the root filesystem is checked. Even with the future version of e2fsprogs, if the time is incorrect, a filesystem check will be forced when it doesn't need to be, which is what users really complain about. Simply changing the message isn't going to keep users from getting upset (and they deserve to be). I had thought the bug was fixed since util-linux moved the hwclock.sh to rcS.d/S8hwclock.sh in version 2.12r-13, and Feisty is using 2.12r- 17ubuntu, but I see that upon closer inspection it looks like Feisty still has hwclock.sh started at S50 (and Debian still has it as S11 instead of S8, argh; so bug #342887 was inappropriately closed in Debian, sigh). So I believe the correct answer at this point is that an Ubuntu task against util-linux needs to be kept open against the Ubuntu util-linux package, since that is where the correct patch should be applied. Does that sound right to you? -- 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 43239] Re: fsck should check against a timestamp "49710 days" old
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 the fix to arrive in Ubuntu, someone should set it to "Won't Fix". ** Changed in: sysvinit (Ubuntu) Status: Invalid => Confirmed -- 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 43239] Re: fsck should check against a timestamp "49710 days" old
** 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 member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 43239] Re: fsck should check against a timestamp "49710 days" old
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 reported issue "fixed" for e2fsprogs. (It is beyond me why you marked this invalid, as you've actually implemented a check against an insane timestamp, which, essentially, this report was originally about - regardless of what actually caused the misadjusted timestamp. Knowing you're the one who wrote e2fsprogs, though, I won't question your decision here. ;-) Then, as a separate issue, I definitely agree that a standard init process (without e.g. a parallel boot messing things up) shouldn't cause such conditions to occur, where fsck has to (unnecessarily) warn about an "insane clock" (even if the fsck now still runs). (You seem to indicate this has been fixed before you added the task for sysvinit, which would mean we can expect the fix to flow downstream to Ubuntu in due course.) -- 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 43239] Re: fsck should check against a timestamp "49710 days" old
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/cgi-bin/bugreport.cgi?bug=342887 In any case, it's not an e2fsprogs issue. Time should be set correctly when e2fsck runs, gosh darn it! ** Changed in: sysvinit (Ubuntu) Status: New => Invalid -- 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 43239] Re: fsck should check against a timestamp "49710 days" old
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 checking the root filesystem. This causes the "last checked" time to be writen out in the wrong time zone, and then if you reboot right away, it causes this problem. 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. But the real, fundamental flaw is that the init scripts aren't correctly making sure that the system clock is accurately set before e2fsck is run. ** Changed in: e2fsprogs (Ubuntu) Status: Confirmed => Invalid ** Also affects: sysvinit (Ubuntu) Importance: Undecided Status: New -- 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 43239] Re: fsck should check against a timestamp "49710 days" old
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 "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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 43239] Re: fsck should check against a timestamp "49710 days" old
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 without checking" error. -- 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 43239] Re: fsck should check against a timestamp "49710 days" old
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 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 43239] Re: fsck should check against a timestamp "49710 days" old
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 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 43239] Re: fsck should check against a timestamp "49710 days" old
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.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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 43239] Re: fsck should check against a timestamp "49710 days" old
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 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 43239] Re: fsck should check against a timestamp "49710 days" old
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. Included is a dmesg of the system concerned for luck. ** Attachment added: "dmesg of affected system" http://librarian.launchpad.net/7337309/dmesg.txt -- 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 43239] Re: fsck should check against a timestamp "49710 days" old
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 Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 43239] Re: fsck should check against a timestamp "49710 days" old
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 target root (/) directory.
When the installation finished and I rebooted my computer, it runs a
filesystem check on my root (/) partition (/dev/sda6) because there had
been no fsck since 49710 days.
--
fsck should check against a timestamp "49710 days" old
https://launchpad.net/bugs/43239
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
