Summary: | sys-fs/e2fsprogs goes through full filesystem check when it detects superblock write time in future | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | PM <mitaspiotr> |
Component: | [OLD] Core system | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED NEEDINFO | ||
Severity: | normal | CC: | gentoo |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://bugs.launchpad.net/e2fsprogs/+bug/107098 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
PM
2009-09-10 13:56:48 UTC
I'm guessing you've set your hardware clock to be in local time, yes? If so, it seems to me to be insane of e2fsprogs to expect that last write time is in the past. Default should be to expect last write time to be < NOW+24HRS Piotr: Please add to this report the output of: grep '^clock' /etc/conf.d/hwclock cat /etc/timezone emerge -pv e2fsprogs piotrek@gentoo ~ $ grep '^clock' /etc/conf.d/hwclock clock="local" clock_systohc="YES" clock_args="" piotrek@gentoo ~ $ cat /etc/timezone Europe/Warsaw piotrek@gentoo ~ $ emerge -pv e2fsprogs These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] sys-fs/e2fsprogs-1.41.9 USE="nls" 0 kB Total: 1 package (1 reinstall), Size of downloads: 0 kB piotrek@gentoo ~ $ *** This bug has been marked as a duplicate of bug 142850 *** This bug is not about fsck babbling about write time in the future, but about going through a full filesystem check during next boot (though someone changed the summary so it looks like a duplicate, I'm changing it now to something more appropriate) except that your error still looks like a dupe. create the /etc/e2fsck.conf as documented in the other bug and verify that rebooting still causes problems. I don't get it. Should I create /etc/e2fsck.conf and write "buggy_init_scripts" to it? If so, it doesn't work. Also the openrc 5.1 (i think it was it) changed it, that now fsck runs during the same boot, but it does not look right. * Checking local filesystems ... Gentoo: Superblok last write time (Sun Oct 11 14:17:16 2009, now = Sun Oct 11 12:17:23 2009) is in the future. Gentoo: NIEOCZEKIWANA NIESPOJNO∎∎; TRZEBA URUCHOMI∎ fsck R∎CZNIE. (tzn. bez opcji -a ani -p) * Fileystem errors left uncorrected, aborting [ !! ]* rc: Aborting! * fsck: caught SIGTERM, aborting* rc-abort: failed to signal parent 1275: No such process * Checking local filesystems ... Gentoo zawiera system plików z b∎∎dami, wymuszono sprawdzenie. Gentoo: 563184/15269888 plików (1.4% nieci∎g∎ych), 46398426/61071073 bloków Gentoo-boot: odtwarzanie z kroniki Gentoo-boot: czysty, 68/26208 plików, 49080/104420 bloków [ ok ]* Remounting root filesystem read/write... I'm seeing the same issue. I installed fresh at the beginning of this year. I just updated my entire "world" except for the kernel. The previous bugs that come up when searching for solutions don't have clear solutions. Could someone please shine some light on this while I try to work through it myself. |