Avoid rename of files not closed

[Spictera]

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

 

[Robert Obkircher]

Can you provide more details like some specific log messages?

Have you tried to change the Data Sync Level from Filesystem to File in the datastore tuning options?

 

[Spictera]

In the fuse filesystem layer I see that the chunk files are open when rename operation is performed.
This causes fuse3 to sometimes create .fuse_hidden_xxxx to avoid issues.

As I understand this, the intention in Proxmox Backup Server is to have some kind of atomic write operations.
I am ok with that, but why not close the file before renaming the chunk files, as it is causing issues in transactional filesystem.

You mentioned some settings?
Which one can change this behavior?

 

[Robert Obkircher]

In the fuse filesystem layer I see that the chunk files are open when rename operation is performed.

Yeah, looks like we always keep the file descriptor open during the rename.

Could you open a bugzilla [1] issue about it?

You mentioned some settings?
Which one can change this behavior?

No setting can change this at the moment.

[1] https://bugzilla.proxmox.com/