#342 export-tar invalid timestamps

Open
opened 3 months ago by jasperla · 1 comments

What I’m trying to do and why

Create a tar export:

borgmatic export-tar --destination jaguar_backup.tar --archive jaguar-2020-07-24T07:36:12.142326

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:

-rw-r--r--  1 root     wheel          351 Jan  1  1970 etc/ssh/sshd_config
drwxr-xr-x  2 root     wheel            0 Jan  1  1970 etc/ssl

Expected behavior (if a bug)

Timestamp should match the original file, e.g.:

-rw-r--r--  1 root  wheel  351 Jul  3 17:03 /etc/ssh/sshd_config

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)

#### What I'm trying to do and why Create a tar export: ``` borgmatic export-tar --destination jaguar_backup.tar --archive jaguar-2020-07-24T07:36:12.142326 ``` #### 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: ``` -rw-r--r-- 1 root wheel 351 Jan 1 1970 etc/ssh/sshd_config drwxr-xr-x 2 root wheel 0 Jan 1 1970 etc/ssl ``` #### Expected behavior (if a bug) Timestamp should match the original file, e.g.: ``` -rw-r--r-- 1 root wheel 351 Jul 3 17:03 /etc/ssh/sshd_config ``` #### 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)
witten commented 3 months ago
Owner

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:

  • Does this reproduce when using Borg directly? You can try running borgmatic with the -v 2 flag, and that should output the borg 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.
  • Are the timestamps correct in the Borg archive? You can see the timestamps within the archive with borgmatic list --archive ...
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: * Does this reproduce when using Borg directly? You can try running `borgmatic` with the `-v 2` flag, and that should output the `borg 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. * Are the timestamps correct in the Borg archive? You can see the timestamps within the archive with `borgmatic list --archive ...`
witten added the
bug
label 3 months ago
witten added the
waiting for response
label 2 months ago
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.