CentOSThis forum is for the discussion of CentOS Linux. Note: This forum does not have any official participation.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
You think its still tarring up those individual files its producing the warning for or it just gives up altogether and fails the whole tar as its producing loads of warnings for individual files?
I don't know. Did you try running tar with the --warning=no-file-changed option?
still no joy im afraid even when i put in at the end of the tar command --warning=no-file-changed the tar still fails
strange thing is when i did tar -cf - after_louise_1606/ | md5sum, it said the exact same things ie the same warning i was getting before but it managed to produce a md5sum string
How about you make a copy of the directory, run the tar on the original directory, then compare the directory with the directory copy you made in order to see if any files or directories have been updated (contents or metadata) in the meantime. If tar says that some files are being changed, you need to find out which ones.
Depending on the results, you can then do the same thing again but without running tar, just pausing 5 minutes or so, to see if it is tar itself that is somehow making the changes.
i think i know what the problem is, its because im running the tar command over an nfs share and not on the local drive, this is why im getting read errors as when i run the tar command on my local disk (copy the data over to my local disk) it creates the tar fine
I still can't see any problem, I don't know why can't you accept: the files were modified during the tar process. Probably they were accessed from another host, I have no idea. But you may have time related problems too.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.