Summary: | timestamp Jan 1, 1970 is altered to Feb 7, 2106 after re-mount of ext3 file system | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Shigeru Akiyama <akyms_hm> |
Component: | [OLD] Core system | Assignee: | Gentoo Kernel Bug Wranglers and Kernel Maintainers <kernel> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | jakub |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
URL: | http://bugzilla.kernel.org/show_bug.cgi?id=5079 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Shigeru Akiyama
2005-08-08 03:12:57 UTC
can you reproduce this problem in any other filesystem type or it just occurs in ext3? Additional information: If I access the same partition from x86 Gentoo, timestamps `Jan 1, 1970' and `Dec 31, 1969' are still there. It seems that function `stat()' on amd64 is behaving strangely. Reply to the previous comment: I don't have an ext2 partition. Correction: I don't have a partition other than ext3. can you please post your timezone? ls -lh /etc/localtime would be ok. root:~# ls -lh /etc/localtime lrwxrwxrwx 1 root root 25 Jul 21 09:00 /etc/localtime -> /usr/share/zoneinfo/Japan can you please try to reproduce this bug in plain vanilla kernel? This bug was found approx. 2 weeks after I had updated the kernel. I am sure all timestamps were OK for that period. It must be some package (or a combination of packages) I installed or updated around Aug. 6-7 that induced this bug. It will be a daunting task to try out packages and more packages. Is there some kind of test script to run to locate a buggy part? You can start by using genlop to reduce the possible packages that 'cause the problem. after that, all you can do is to try reinstall some packages that can 'cause that kind of breakage on the system... It's almost certainly a kernel thing. Please just confirm the problem still exists on the latest development kernel (currently vanilla-sources-2.6.13_rc6) I have tested `vanilla-sources-2.6.13_rc6'. Still, timestamp Feb 7, 2106 is displayed instead of Jan 1, 1970. Closing as upstream bug. |