Thank you for your answer. I am aware that's not an optimal solution, K. For what i can understand here: https://backuppc.github.io/backuppc/BackupPC.html#What-type-of-storage-space-do-I-need
Starting with 4.0.0, BackupPC no longer uses hardlinks for storage of deduplicated files. However, hardlinks are still used temporarily in a few places for doing atomic renames, *with a fallback doing a file copy if the hardlink fails*, and files are moved (renamed) across various paths that turn into expensive file copies if they span multiple file systems. So there is a "fallback" if the filesystem does not support hardlinks. Or maybe I got that wrong (I am not an English mother tongue speaker)... > ---------- Forwarded message ---------- > From: backu...@kosowsky.org > To: "General list for user discussion, questions and support" < > backuppc-users@lists.sourceforge.net> > Cc: > Bcc: > Date: Fri, 2 Sep 2022 14:31:18 -0400 > Subject: Re: [BackupPC-users] errors on network-mounted pool filesystem > Are you sure that BackupPC is compatible with sshfs? > While v4 drastically reduces number of hard links by eliminating the > hard-link pool scheme, it still uses hard links for *temporary* atomic > renames. > See: http://backuppc.sourceforge.net/BackupPC-4.2.1.html > > Sshfs may have other limitations as it is not a full-fledged > filesystem... > >
_______________________________________________ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List: https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki: https://github.com/backuppc/backuppc/wiki Project: https://backuppc.github.io/backuppc/
