Unknown unix metadata version +12

Server
1

Hello everybody and Merry Christmas,

I have been using UrBackup in a business environment for about 1.5 years now and have not had any major problems so far.

But since a few days I have got an error message in the backup log of a client, which I can’t get on with:

Unknown unix metadata version +12 in "/mnt/backup/urbackup_tmp_files/78"

I even reformatted the backup hard disk (/mnt/backup/), the SMART values are good and it’s only one client that is causing problems.

Do you have an idea how I can get ahead here? Here is some technical information:

Server

  • Debian Buster 10.2 in a VM on a Proxmox-Host
  • UrBackup Server 2.4.12

Client

  • Debian Stretch (9.11), a Proxmox-Host
  • UrBackup Client 2.4.9.0 (going to update this one)

Thanks in advance!

2

The log line should be followed by “Copied metadata to FN for error analysis”. If possible send that file to bugreports@urbackup.org (it contains file metadata of all the files being backed up).

3

I’m not sure where I can find that file, there’s also no such line in the log?

13
13959×220 25.3 KB

4

Can you change the code? If yes change https://github.com/uroni/urbackup_backend/blob/c7c80cc5636496ade779f8b37dbfbfbd6eaca02f/urbackupserver/FileMetadataDownloadThread.cpp#L454

if (isComplete())

to

if(true)

5

You do get the Error saving metadata. Could not save OS specific metadata to FN later?

Edit: If possible please post the whole log with log level information.

6

I’m using the debian packages, so I’m not sure if I can change the code without installing from source?

You do get the Error saving metadata. Could not save OS specific metadata to FN later?

No, no occurrence of that message. I attached the full log.

logfile.txt (155,3 KB)

7

Seems it is a debug level message. So if you put the server into debug logging mode it should go into the log file (see Having problems with UrBackup? Please read before posting )

8

Installing from source shouldn’t be that hard. See https://www.urbackup.org/server_source_install.html

Symlink the db location beforehand (mkdir -p /usr/local/var && ln -s /var/urbackup /usr/local/var/urbackup) and install a few dependencies (apt install build-essential zlib1g-dev plus perhaps a few configure tells you about)

9

I’ve sent the debug log to bugreports@urbackup.org.

10

Hello. Was this issue resolved? I’m getting these errors on one machine:

Errors 06/07/23 11:44 Unknown unix metadata version +12 in “/opt/urbackup/storage/urbackup_tmp_files/5”
Errors 06/07/23 11:44 Error saving metadata. Could not save OS specific metadata to “/opt/urbackup/storage/xxx-pve/230607-1143/.hashes/pve/openvz”

Server: 2.5.31 on Ubuntu 22.04, storage on ZFS
Client: 2.5.23 on Proxmox VE (Debian Bullseye) with XFS, no snapshot mechanism configured

11

I just had the same issue trying UrBackup for the first tgime with Proxmox v8

Errors 05/09/23 14:02 Unknown unix metadata version +12 in “T:\UrBackup\TMP\urbackup_tmp\urb6318f76425df34160000000140114D287.tmp”
Errors 05/09/23 14:02 Error saving metadata. Could not save OS specific metadata to “D:\UrBackup\stu\230905-1401.hashes\etc\pve\local”

Server: 2.5.31 on Windows Server 2022, storage on ReFS
Client: 2.5.24 on Proxmox VE (Debian Bookworm) with ZFS, no snapshot mechanism configured

I’ll dig around for more logging, but was hoping that maybe there was a way to resolve from the original problem reported