ERROR: not on mount point: /

[MarkoSchuetz]

I'm seeing the following in the logs:

Apr 22 09:02:20 tpad-m snapsync[23325]:  WARN  Snapsync : failed to synchronize root on /run/media/marko/snapsync/root
Apr 22 09:02:20 tpad-m snapsync[23325]:  WARN  Snapsync :   btrfs failed
Apr 22 09:02:20 tpad-m snapsync[23325]:  WARN  Snapsync :     receive /run/media/marko/snapsync/root/1151: ERROR: empty stream is not considered valid
Apr 22 09:02:20 tpad-m snapsync[23325]:  WARN  Snapsync :     send -p /.snapshots/1086/snapshot /.snapshots/1151/snapshot: ERROR: not on mount point: /

There is also a snapshot that seems to be left over from this:

single | 1206 |       | Sun 22 Apr 2018 09:02:14 AM AST | root |          | synchronization snapshot for snapsync | important=yes, snapsync=c2c281a6-788e-4852-b3c8-4042b00aa9ba, snapsync-description=local:/run/media/marko/snapsync/root

[MarkoSchuetz]

Seems to be related to this

[doudou]

Unfortunately, I stopped using btrfs (and therefore snapsync), after having lost hours on balancing issues as recently as last december. I don't have time for this.

Snapsync is indeed leaking synchronization snapshots on error. I've never bothered fixing it as they get cleaned up on the first successful synchronization.

[MarkoSchuetz]

What do you use instead of btrfs?

[doudou]

Right now, I'm using xfs + restic (with snapsync's little brother, restic-service, to automate backups through restic).

I'm not too unhappy, but not too happy either with this setup. There's the obvious lack of "free" snapshots. But there's also (and more importantly) the fact that restic takes really a lot of CPU.

[daiaji]

To be honest, although btrfs is not robust, it is still one of the few modern file system solutions natively supported by linux. You can also try ZFS, but the ZFS module will be damaged every time the kernel is updated, which is unavoidable (That is, the NVIDIA driver will bring out problems), so the update can only be postponed. After all, they are all kernel modules outside the tree, and the ease of use will always be quite bad. Of course, btrfs is a last resort choice, at least it can still be used.