Bug 1283843
Summary: | newer ignored | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Richard Jasmin <spike85051> |
Component: | tar | Assignee: | Pavel Raiskup <praiskup> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 23 | CC: | kdudka, ovasik, praiskup, spike85051 |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-12-21 07:34:40 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Richard Jasmin
2015-11-20 05:02:00 UTC
Richard, thanks for this report but I got lost. The --newer option compares against ctime, --newer-mtime against mtime. Did you want to use --newer-mtime instead? not sure. I dont want "today". +/-30 would suffice but how to do this above you need an actual date like 1-Nov. I want some date in the past.IE: my last backup date. "newer" expects one day past that(for repeated instances) but is having an issue checking the file date for some reason. mtime sounds correct. Again a documentation glitch. Sound be documented but may not be. Now we are getting windows dates in here too. IE: if a file was modified on windows vice linux. Do I need to touch everything and try a full backup again? Because if I touch everything and do an incremental, I might as well be doing a full. But shouldnt other simple commands like: move, copy,... use this as well? No matter what "time" option Ive used, Im geting the same result, as if Linux cant track dates for some reason.I dont believe Ive disabled access time on /home. What you said seems to do the trick but only with tar. (In reply to Richard Jasmin from comment #2) > not sure. > I dont want "today". > +/-30 would suffice but how to do this above you need an actual date like > 1-Nov. I want some date in the past.IE: my last backup date. > > "newer" expects one day past that(for repeated instances) but is having an > issue checking the file date for some reason. > > mtime sounds correct. Again a documentation glitch. Sound be documented but > may not be. I think it is documented, try: $ info tar "after" > Now we are getting windows dates in here too. IE: if a file was modified on > windows vice linux. Do I need to touch everything and try a full backup > again? Because if I touch everything and do an incremental, I might as well > be doing a full. I don't understand this part of your response. As far as 'mtime' comparison works for you, don't hesitate to use it. > But shouldnt other simple commands like: move, copy,... > > use this as well? No matter what "time" option Ive used, Im geting the same > result, as if Linux cant track dates for some reason.I dont believe Ive > disabled access time on /home. The 'mv' and 'cp' from coreutils have '-u' option which also looks at 'mtime'. But I'm not the right person to give you the help here, I would suggest you to contact upstream coreutils. > What you said seems to do the trick but only with tar. Maybe I have difficulties to understand the issue - but it looks the tar is fine here. Richard, please reopen if you feel otherwise. |