Hi
The Proxmox Backup Server are doing renames of files not closed.
This causes several issues.
1. A fuse3 mounted filesystem as backend/target filesystem for Proxmox Backup Server will rename the files to .fuse_hidden_Nnnnn to avoid crashes.
2. Using a transactional filesystem as a target cannot work, as the file does not exist until it is closed. So a rename that are executed before the file is closed will result in an error that the file does not exist.
3. The targeted filesystem is a WORM based filesystem.
Is there a way to avoid these atomic write/rename of files, as the filesystem anyway uses this as it is transactional.
Eg in /etc/vzdump.conf there is a way to set temporary files to be stored elsewhere, but is there any equal for Proxmox Backup Server?
Or is this just a bug or design as intentional?
Regards Tomas
The Proxmox Backup Server are doing renames of files not closed.
This causes several issues.
1. A fuse3 mounted filesystem as backend/target filesystem for Proxmox Backup Server will rename the files to .fuse_hidden_Nnnnn to avoid crashes.
2. Using a transactional filesystem as a target cannot work, as the file does not exist until it is closed. So a rename that are executed before the file is closed will result in an error that the file does not exist.
3. The targeted filesystem is a WORM based filesystem.
Is there a way to avoid these atomic write/rename of files, as the filesystem anyway uses this as it is transactional.
Eg in /etc/vzdump.conf there is a way to set temporary files to be stored elsewhere, but is there any equal for Proxmox Backup Server?
Or is this just a bug or design as intentional?
Regards Tomas