Dan Nelson wrote:
If it's always the same file at fault, it might be interesting to print the results of ls -l on the file just before and after the tar run (or modify gtar to print the two values at part of the error message).
It is, but adding an ls statment before and after fixes the problem. I might try the option to modify gtar to see what's going on. And consider using a modified tar which is not as picky for my xenofarm environment. Seems like the cleanest solution unless someone else is striken by the same problem.
// Mikael