On Sun, Feb 18, 2007 at 12:47:57AM -0300, Gabriel Parrondo wrote: > El dom, 18-02-2007 a las 02:48 +0000, David Dawson escribió: > > David Dawson wrote: > > > > > Running Debian Etch on an AMD Athlon 2100+ ECS motherboard with 3 hard > > > disks, the 40 G original hard disk was showing inodes date in future on a > > > user forced fsck. > > > The reason the user forced the fsck was because of a system sluggishness > > > he suspected problems and rebooted with a forced fsck. > > > > > > I have installed etch on another of his hard disks and moved over his home > > > directory to the new disk. > > > > > > Does anyone have an idea what would have put inodes dates in the future on > > > this drive only and would this have caused a disk slowdown? It wouldn't be > > > swap issues, I think, since the machine has 2G of RAM. > > > > > > Thanks > > OOPS, forgot to say that it's running Debian kernel 2.6.18-3-k7 > > -- > > > Usually, this happens when you mount the file-system on the disk from a > live cd . The reason, I think, is that the LiveCD doesn't configure its > date correctly and if you write to the disk, it gets written on the > future (from the installed distro point of view). > > > Please someone correct me if I'm wrong. sounds reasonable to me. Of course that atime might have to be pretty far into the future. OP, what version of e2fsprogs are you running? there were some issues with e2fsprogs freaking out because of a change in the way the system clock was handled during boot. The result was a massive pile of fsck errors because atimes were in the future (not really, but e2fsck thought they were). my memory is foggy on this though. I think it was 1-2 years ago though. You should be long past that problem. A
Attachment:
signature.asc
Description: Digital signature