topic Re: tar error - file changed size in Operating System - HP-UX

tar error - file changed size

Ian Lochray — Thu, 06 Sep 2001 12:48:20 GMT

I have a backup script which uses tar to back up files. I cannot use fbackup as the script has to work on multiple platforms. Occasionally, I get an error from tar saying that a file has changed size. I have seen references to this error in previous postings and some of the replies state that the error (and other errors that give a return code of 5) is non-fatal.
Does "non-fatal" mean that the file is correctly backed up or just that the error is not serious enough to stop tar in its tracks?

Re: tar error - file changed size

John Bolene — Thu, 06 Sep 2001 13:05:32 GMT

You have tarred to a file in the same directory such as

tar -cf stuff *

this will also try to tar the stuff file into itself, bad thing to do
cd /tmp
tar -cf stuff /other-dir
will create the stuff file in /tmp

Re: tar error - file changed size

A. Clay Stephenson — Thu, 06 Sep 2001 13:06:40 GMT

Hi:

It means that while being backed up a file was modified (typically appended) by another process. Whether this is bad or not depends on the application. If it is a database it is almost certainly very bad. One way to avoid these kinds of errors is to do an OnlineJFS snapshot mount and backup the snapshot. The snapshot takes only a few seconds and then all the snapshot files are certain to remain constant while the 'real' files can remain in use.

Clay

Re: tar error - file changed size

Ian Lochray — Thu, 06 Sep 2001 13:21:24 GMT

John,
the tar is to a tape, not to a file.
Clay,
unfortunately, many of our customers do not have online JFS. The file is not a database file. As you suggest, it is appended to periodically. It appears that the backup is coinciding with one of these periods.

Re: tar error - file changed size

Sanjay_6 — Thu, 06 Sep 2001 17:07:54 GMT

Hi,

As clay told you, the file got modified (appended or reduced) during the backup. does not look that serious to me, until the file is very important. There is no choice over this other than online JFs where you can create a snapshot and back that up. That is the only way you can be certain that you have a backup whcih matches the state of you file when the snapshot was taken. Otherwise learn to live with the error message you are getting. No harm in that.

Thanks