Re: Inodes date in future - problem

2007-02-18 Thread David Dawson
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 reboot

Re: Inodes date in future - problem

2007-02-17 Thread Andrew Sackville-West
On Sun, Feb 18, 2007 at 12:47:57AM -0300, Gabriel Parrondo wrote: > El dom, 18-02-2007 a las 02:48 +, 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

Re: Inodes date in future - problem

2007-02-17 Thread Kevin Mark
On Sun, Feb 18, 2007 at 12:47:57AM -0300, Gabriel Parrondo wrote: > El dom, 18-02-2007 a las 02:48 +, 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

Re: Inodes date in future - problem

2007-02-17 Thread Gabriel Parrondo
El dom, 18-02-2007 a las 02:48 +, 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 fsc

Re: Inodes date in future - problem

2007-02-17 Thread David Dawson
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 reboot

Inodes date in future - problem

2007-02-17 Thread David Dawson
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