fbackup modifying inode time?

[Brian K. Arnholt]

I have a script that does an "ls -tc" to sort files based on their inode modification time. I noticed during an fbackup session to a remote device that it changes the inode modification time of the file to the current time as fbackup progresses (the actual file mod. time remains unchanged).

Does anyone know of a bug with fbackup that causes it to change inode modification times?

we're using a JUN, 2002 version of HP-UX 11.00).

Thanks!

[Sundar_7 · Accepted solution]

That is how fbackup works Brian. It is a known limitation.

From the man page of fbackup

" Due to present file-system limitations, files whose inode data, but
not their contents, are modified while a backup is in progress might
be omitted from the next incremental backup of the same graph. Also,
fbackup does not reset the inode change times of files to their
original values."

But I dont know if there is a work around for this.

[Brian K. Arnholt]

Thanks Sudar, I was too lazy to find this in the man pages. We used to have an old C240 with a Sep, 99 version of HP-UX 11.00 that I don't recall this being a problem.

No big deal, I'll just revamp my script.

[Brian K. Arnholt]

Come to think if it, with our previous system, our file systems used to be HFS, rather than JFS as with our systems now. That probably is the reason why.

Brian