Re: Re: Perfomance problem backupscript (more details and tests)
Joerg Schilling <[email protected]>
| Newsgroups | gmane.comp.archivers.star.user |
|---|---|
| Message-ID | <43466D44.nail226N54KV@burner> |
David Brown <[email protected]> wrote: > On Thu, Oct 06, 2005 at 01:14:04PM +0200, [email protected] wrote: > > > The ctime-quirk seems to be dependend on the type of > > filesystem and on the version of Linux. It has been > > patched into the code without revising documentation. > > It might get patched out of the code as well. > > http://sourceforge.net/mailarchive/forum.php?thread_id=3726620&forum_id=6379 : > > "Unfortunately, however, the change was not pushed > > into 2.3, and so 2.4 and now 2.6 have a ext2 rename() > > implementation that does not update inode ctime." > > Given that ctime's purpose was to allow correct incremental backups, not The reason for the existence of st_ctime is that you need it in case that someone set st_mtime to an old value. Jörg -- EMail:[email protected] (home) Jörg Schilling D-13353 Berlin [email protected] (uni) [email protected] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily