On Tue, 2003-12-16 at 10:57, Harry Putnam wrote: > Tim Littlemore <support@xxxxxxxxxxxxx> writes: > > newest version of the kernel through the up2date service fix this problem? > > > > The only reason you've never seen this before is just conincidence. It isn't a > > bug or anything, it's just tar telling you that as it was tarring the file > > up, the contents of it changed. This is pretty common when tarring log files. > > It isn't a problem as such, it just means that the version of the file in your > > tar won't match the current version of that file. > > > > There's nothing you can do to the kernel to stop this. > > Not to be a wiseacre but: > Are you sure of this? I've seen this for the first time recently too > and have used tar extensively since about 1996. I notice it only > when taring files on a dos partition. Further it seemed to go away > when I moved the file to ext3 then tarred. > For what it is worth, I have also had this problem when tar'ing up movies over an SMB share, I am fairly certain that they arn't being changed by a user or any thing along those lines as the machine it's on is not being used. However, some thing else in the back ground may be doing it. Doug
