Critical errors when creating a new RSYNC snapshot (and the percentage is wrong)

[Templayer]

Creating new snapshot...(RSYNC)
Saving to device: /dev/nvme0n1p6, mounted at path: /run/timeshift/backup
Linking from snapshot: 2022-04-12_10-00-02
Synching files with rsync...
9.60% complete (00:00:09 remaining)
 17.68% complete (00:00:04 remaining)
 40.49% complete (00:00:02 remaining)
 51.51% complete (00:00:02 remaining)
 64.28% complete (00:00:02 remaining)
 76.73% complete (00:00:01 remaining)
 87.14% complete (00:00:00 remaining)
 97.00% complete (00:00:00 remaining)
104.63% complete (00:00:00 remaining)
119.05% complete (00:00:00 remaining)
130.43% complete (00:00:00 remaining)
148.26% complete (00:00:00 remaining)
162.19% complete (00:00:00 remaining)
179.82% complete (00:00:00 remaining)
197.75% complete (00:00:00 remaining)
208.46% complete (00:00:00 remaining)
220.14% complete (00:00:00 remaining)
228.46% complete (00:00:00 remaining)
256.12% complete (00:00:00 remaining)
273.35% complete (00:00:00 remaining)
286.72% complete (00:00:00 remaining)
300.44% complete (00:00:00 remaining)
313.88% complete (00:00:00 remaining)
328.80% complete (00:00:00 remaining)
(process:194401): GLib-GIO-CRITICAL **: 15:56:33.784: g_output_stream_clear_pending: assertion 'G_IS_OUTPUT_STREAM (stream)' failed
(process:194401): GLib-GIO-CRITICAL **: 15:56:33.784: g_output_stream_clear_pending: assertion 'G_IS_OUTPUT_STREAM (stream)' failed
Stream has outstanding operationE: Error opening file “/run/timeshift/backup/timeshift/snapshots/2022-04-12_15-56-09/rsync-log-changes”: File exists
E: Failed to write file: /run/timeshift/backup/timeshift/snapshots/2022-04-12_15-56-09/rsync-log-changes
329.15% complete (00:00:00 remaining)

Might not be bauh's fault.

Looks fine in Timeshift:

Software Environment bauh version: 0.10.2 O.S: Linux Mint 20.3 Una with Cinnamon; kernel: 5.4.0-107-generic Python version: Python 3.8.10 Installation method: pip3

[vinifmor]

This seems to be a Timeshift issue. This whole output comes from Timeshift (bauh doesn't touch it). You can try executing the command through a CLI and see if the output is the same: 'timeshift --create --scripted --rsync --comments "<bauh>"

[Templayer]

Reported in https://github.com/teejee2008/timeshift/issues/885

[Templayer]

I'll try that later, because currently I'm too low on space.

I'll probably have to partition my storage drive to make an ext4 partition just for backups and put backups there.

It's really too bad that Timeshift/rsync don't support saving into NTFS drives into tarballs (to preserve Linux permissions). Wouldn't have to be compressed. Even though that option would be neat too.

[Templayer]

This whole output comes from Timeshift (bauh doesn't touch it).

Closing as this is not a bauh issue.

[Templayer]

This seems to be a Timeshift issue. This whole output comes from Timeshift (bauh doesn't touch it). You can try executing the command through a CLI and see if the output is the same: 'timeshift --create --scripted --rsync --comments ""

I'll try that later, because currently I'm too low on space.

I'll probably have to partition my storage drive to make an ext4 partition just for backups and put backups there.

jboksa1@JB-PC:~$ sudo timeshift --create --scripted --rsync --comments "<bauh>"

/dev/sda2 is mounted at: /run/timeshift/backup, options: rw,relatime

------------------------------------------------------------------------------
Creating new snapshot...(RSYNC)
Saving to device: /dev/sda2, mounted at path: /run/timeshift/backup
Linking from snapshot: 2022-04-13_12-12-16
Synching files with rsync...
Stream has outstanding operationStream has outstanding operation341.72% completeCreated control file: /run/timeshift/backup/timeshift/snapshots/2022-04-13_12-45-09/info.json
RSYNC Snapshot saved successfully (42s)
Tagged snapshot '2022-04-13_12-45-09': ondemand
------------------------------------------------------------------------------