TW
23 test fails: - create_test_files: os.mknod -> Function not implemented (ENOSYS) (with root it works, so just a bad errno?) - solved by #1963. - get_acl (from linux platform module)...
Docs updated, see PR #1962.
@Clete2 borg check (in full mode, not just in --repository-only mode) being ok is quite a good sign already. a more practical test is to actually extract all data again...
Well, maybe a matter of taste, but I find anything major starting automatically on startup (or shutdown) rather annoying.
Often or always? Maybe syncing a dir is not supported on windows?
``` import errno import os import sys def sync_dir(path): fd = os.open(path, os.O_RDONLY) try: os.fsync(fd) except OSError as os_error: # Some network filesystems don't support this and fail with EINVAL....
so, the "linux filesystem" syncs dirs ok (in WSL), but the mounted drvfs always fails with the dir sync?
\synology\Backups is what? smbfs via drvfs? Guess that's a bug in one of these filesystems. They should either support dir sync or say "invalid" (EINVAL), but not "I/O error" (EIO).
## bsdflags ### borg 1.2 behaviour, create - with `--noflags` the bsdflags are not read and the value is set to 0 - otherwise the flags value is read from...
## xattrs ### borg 1.2 behaviour, create - with `--noxattrs`, the xattrs are not read and no xattrs key is stored into the item attrs - otherwise the xattrs are...