6/29/2023 0 Comments Syncthing ignore by extensonThe solution, however, breaks nothing and is simple just include default ignore lists. I have a few projects of mine corrupted and had to rm -rf. Syncthing by default can and will corrupt. There is a much stronger point here about usability by default a backup software should never corrupt what is already there. I bet this number is fairly high, meaning we should not ignore a large portion of our current user base. git is a niche tool but consider this: the number that really matters here is the conditional probability of a syncthing user also using git aka p(uses git | uses syncthing). git/* objects unpredictably - it doesn't happen all the time and doesn't corrupt all the repos just happens sometimes for some repos under some weird race(?) conditions. So far, trying to sync a folder which somehow contained (not directly) a version control repository (e.g.git) corrupts the. Regardless of what platform we're on, we should use the same default excludes for consistency (and because people do share storage devices between systems). local/share/trash is the per-user trash-can for XDG compliant desktop environments on Linux (which is 90% of what people who use X use on Linux). gvfs is found in most people's home directories on Linux when they use most desktop environments other than KDE, and shouldn't be scanned because it covers dynamic access to access transiently connected and non-filesystem items (network filesystems, archives, MTP devices, etc) I'm not 100% certain what OS it's from, but it looks like ancillary volume metadata (which makes me think it's probably OS X), so it probably shouldn't be synced. fseventsd is something I see a lot on removable media. I've only ever seen this on the C: drive, but I think it shows up on a different drive if there's not enough room on C. $WINDOWS.~BT is a temporary directory used for OS upgrades on Windows (and is often huge if it exists). Yet, it's inefficient in terms of resource usage.$RECYCLE.BIN (case insensitive, since newer Windows versions use $Recycle.Bin) is the per-drive recycling bin for Windows Since it's a CoW file system, creating many directories of the same content, and scheduling rsync to keep up to date is possible. Yet on the secondary (soon to be equal) server/controller/pot, syncthing does not run in a container. On the main 'server', docker is used, so one underlying directory can be expressed as 2 different directories to syncthing, where the second directory is using /dir/.stignore2:/dir2/.stignore:rw. what alternatives or workarounds you considered The prefixes get in the way of sorting the files. ² Planning to switch to suffix, as devices I use this feature with are not Windows, and as such don't rely on file endings. This allows multiple rw shares without major conflicts. The controllers do not transfer data between other controllers using the share(s) other devices use. The share between controllers syncs all files, including the ones ignored by other shares. Around half of the files are only on controllers, yet ready to sync on need. Individual files or whole directories of the multi-TiB shares may be synced with devices based on the device's storage capabilities.
0 Comments
Leave a Reply. |