Can fsck change ctime of an inode?

From: Irene A. Shilikhina (irene@alpha.iae.nsk.su)
Date: Mon Feb 10 2003 - 06:48:14 EST


I suddenly discovered that old directories (older than 5 days) in
/var/adm/syslog.dated remained where they were. I made sure that the
crontab was submitted and it contained an appropriate line:

40 4 * * * find /var/adm/syslog.dated -depth -type d -ctime +5 -exec rm
-rf {} \;

Then I ran 'find /var/adm/syslog.dated -type d -ctime +5' by hand and,
much to my surprise, the output was empty. But 'mtime' instead of 'ctime'
gave what I expected. At this point it occured to me that this server had
experienced crash (with panic 'kernel memory fault'). It happened 9 days
ago.

I removed them anyhow, and 'find' with -ctime +1, +2, +3 , +4 gives the
right result.

Is it possible that fsck after the crash 'cured' these directories so that
ctime in their inodes changed? At boot time my eye had not enough time to
catch all the messages on the screen.

Thanks,
Irene

*************************************************************************
* *
* Irene A. Shilikhina e-mail: irene@alpha.iae.nsk.su *
* System administrator, *
* Institute of Automation & Electrometry, *
* Siberian Branch of Russian Academy of Sciences, *
* Novosibirsk, Russia *
* http://www.iae.nsk.su/~irene *
*************************************************************************
* *
* The road to hell is paved with good intentions. *
* *
*************************************************************************



This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:49:07 EDT