export-tar invalid timestamps #342
Labels
No Label
bug
data loss
design finalized
good first issue
new feature area
question / support
security
waiting for response
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: borgmatic-collective/borgmatic#342
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What I'm trying to do and why
Create a tar export:
Steps to reproduce (if a bug)
borgmatic export-tar --destination jaguar_backup.tar --archive jaguar-2020-07-24T07:36:12.142326
tar -tvf jaguar_backup.tar
Actual behavior (if a bug)
All files in the archive have a timestamp of the epoch:
Expected behavior (if a bug)
Timestamp should match the original file, e.g.:
Other notes / implementation ideas
Environment
borgmatic version: 1.5.9
borgmatic installation method: OpenBSD package
Borg version: 1.1.13
Python version: 3.8.3
Database version (if applicable): N/A
operating system and version: OpenBSD 6.7-current (using bsdtar, not gnu tar)
Thank you for reporting this! Unfortunately I can't seem to reproduce the problem locally (Linux + GNU tar); all files come out with the proper timestamps here.
Some ideas on things to try:
borgmatic
with the-v 2
flag, and that should output theborg export-tar
command-line that borgmatic is running. If you run that directly, that should tell you whether the timestamps are still wrong with Borg.borgmatic list --archive ...
Closing due to inactivity. Please feel free to reopen if you have more info to post!