©XSIBackup-Free: Free Backup Software for ©VMWare ©ESXi

Forum ©XSIBackup: ©VMWare ©ESXi Backup Software


You are not logged in.

#1 2021-09-28 14:09:42

michib
Member
Registered: 2020-02-02
Posts: 25

XSIbackup-DC 1.5.1.1 - error 2516/2833 while pruning on a Synology Box

Dear,

While pruning on a Synology Box one backup out of our Repository I get error 2516/2833 at file common.c line 2516/2833. Overral exit code is 0 thou... and exits with success. Happens with versione 1.5.0.x and 1.5.1.1.

V. 1.5.0.x

2021-09-28T15:51:33 | Error code 2516 at file common.c, line 2516 | Error description: can't open fd_tmp_f2edit file

V. 1.5.1.1

2021-09-28T16:18:24 | Error code 2833 at file common.c, line 2833 | Error description: can't open fd_tmp_f2edit file
-------------------------------------------------------------------------------------------------------------
2021-09-28T16:18:24 | Error code 843 at file prune.c, line 843 | Error description: Can't add block count info to: 

Full command and log:

bash-4.3# /usr/bin/xsibackup --prune /volume2/BackupsVMs/Repositorya/IM/20210906070000/
|---------------------------------------------------------------------------------|
||-------------------------------------------------------------------------------||
|||   (c)XSIBackup-Free 1.5.1.1: Backup & Replication Software                  |||
|||   (c)33HOPS, Sistemas de Informacion y Redes, S.L. | All Rights Reserved    |||
||-------------------------------------------------------------------------------||
|---------------------------------------------------------------------------------|
                   (c)Daniel J. Garcia Fidalgo | info@33hops.com
|---------------------------------------------------------------------------------|
System Information: Linux, Kernel 4 Major 4 Minor 59 Patch 0
-------------------------------------------------------------------------------------------------------------
PID: 30079, Running job as: root
-------------------------------------------------------------------------------------------------------------
- Pruning '/volume2/BackupsVMs/Repository/IM/20210906070000'...
- Ordered and unique blocks: 1892569, Index depth was set to : 6
- 100.00% | removed 16046 from 266367 blocks in folder | 14.10 GB were liberated
- Deleting blocks from .blocklog file...
2021-09-28T16:18:24 | Error code 2833 at file common.c, line 2833 | Error description: can't open fd_tmp_f2edit file
-------------------------------------------------------------------------------------------------------------
2021-09-28T16:18:24 | Error code 843 at file prune.c, line 843 | Error description: Can't add block count info to: /volume2/BackupsVMs/Repository/.xsitools
-------------------------------------------------------------------------------------------------------------
- Removed backup folder: /volume2/BackupsVMs/Repository/IM/20210906070000
The --prune process finished (1)
-------------------------------------------------------------------------------------------------------------
Removed PID                   OK
-------------------------------------------------------------------------------------------------------------

PS: why is it that error number and line number are always the same? Seems weird...

thanks,
best regards,
Michele

Last edited by michib (2021-09-28 14:22:52)

Offline

#2 2021-09-29 12:16:51

admin
Administrator
Registered: 2017-04-21
Posts: 1,821

Re: XSIbackup-DC 1.5.1.1 - error 2516/2833 while pruning on a Synology Box

The most likely cause is that you run out of space in the /tmp dir.
Extend the /tmp volume.

Using a closed down propietary device as your NAS has some serious drawbacks, try to use some full fledged Linux FS when you have some more exigent requirements.

If your set of VMs is of a contained size, default Synology configuration might very well be more than enough. When you start to manage big multi-terabyte repos you need control on the NAS OS, which you don't fully have with closed NAS boxes.

Offline

#3 2021-10-09 10:19:39

michib
Member
Registered: 2020-02-02
Posts: 25

Re: XSIbackup-DC 1.5.1.1 - error 2516/2833 while pruning on a Synology Box

Dear,

I raised XSIbackup log verbosity to 10:

- 100.00% | removed 4341 from 49665 blocks in folder | 2.26 GB were liberated
- Deleting blocks from .blocklog file...
Allocated blklogarr0 buffer (120746184 bytes)
-------------------------------------------------------------------------------------------------------------
Allocated blklogarr1 buffer (120746184 bytes)
-------------------------------------------------------------------------------------------------------------
blklogarr0 was qsorted
-------------------------------------------------------------------------------------------------------------
Duplicate blocks removed
-------------------------------------------------------------------------------------------------------------
Allocated blklogarr1 uniqued buffer (120746184 bytes)
-------------------------------------------------------------------------------------------------------------
pruneblks (4341) was qsorted
-------------------------------------------------------------------------------------------------------------
- 4341 blocks removed from the .blocklog file
2021-10-09T12:07:56 | Error code 2833 at file common.c, line 2833 | Error description: can't open fd_tmp_f2edit file
-------------------------------------------------------------------------------------------------------------
2021-10-09T12:07:56 | Error code 843 at file prune.c, line 843 | Error description: Can't add block count info to: /volume2/BackupsVMs/Repository/.xsitools
-------------------------------------------------------------------------------------------------------------
- Done deleting blocks from .blocklog file

It seems is raising that error when rewriting blocklog which is on that repository MBs in size...

admin wrote:

The most likely cause is that you run out of space in the /tmp dir.
Extend the /tmp volume.

This NAS has 2G /tmp space ... it seems unlikely it needs to allocate more than 2GB isnt it? Also you state in full manual that: "©XSIBackup-DC uses just RAM to --prune since version 1.4.2.3, you don't need to worry about having enough tmp space. In case you run out of RAM (you will know because an error will be raised stating that fact), just add more RAM to prune the repo or size your repos to the amount of available RAM."


Using a closed down propietary device as your NAS has some serious drawbacks, try to use some full fledged Linux FS when you have some more exigent requirements.

If your set of VMs is of a contained size, default Synology configuration might very well be more than enough. When you start to manage big multi-terabyte repos you need control on the NAS OS, which you don't fully have with closed NAS boxes.

While I understand you point it I must admit this days Synology makes very performant boxes it would be unfair to say you cannot use this boxes to hold multi-terabyte repos. Why don't you support them? Maybe we could also have some specific app as XSI repository backend.

PS: I'm trying to prune backups on my NAS because rotating them on ESXis is a nightmare: segfaults / malloc errors (which are likely to happen due to shell restrictions I think) there. I'll open another thread.

PS2: I'm also a developer. If you could put at level >5 more debug info it could be easier to find out problems... For example loggin perror() on fopen() failing

thanks,

regards,
Michele

Last edited by michib (2021-10-09 10:35:48)

Offline

#4 2021-10-10 20:37:24

admin
Administrator
Registered: 2017-04-21
Posts: 1,821

Re: XSIbackup-DC 1.5.1.1 - error 2516/2833 while pruning on a Synology Box

The error happens right at the end of the prune process when opening the .xsitools file to change the blocks figures. Your data is OK, still the .xsitools info is outdated.

It's not critical, still we should find out what's going on. Maybe some other process has the file open or the volume is damaged.

Run your command as:

strace /usr/bin/xsibackup --prune /volume2/BackupsVMs/Repositorya/IM/20210906070000/

That will offer you system call level info.

Synology is great, still, you can't install what you want, you have no real root control over it.
You can't use it to recover granular data, as it lacks FUSE
The CPUs are more limited in power when compared to a PC of the same price, etc...

Offline

#5 2021-10-20 07:53:04

michib
Member
Registered: 2020-02-02
Posts: 25

Re: XSIbackup-DC 1.5.1.1 - error 2516/2833 while pruning on a Synology Box

Dear,

Here's the relevant part of strace output. Tell me if you need else.

read(4, "329c45e893d27f69;1048576\nfffb405"..., 4096) = 4096
read(4, "c10f9f63230758890c1b33adef830091"..., 4096) = 4096
read(4, "e3b98a6;1048576\nfffe24a4b1e76c1a"..., 4096) = 4096
read(4, "c0ceb1099a54aed5418552e;1048576\n"..., 4096) = 1502
read(4, "", 4096)                       = 0
lseek(4, 0, SEEK_SET)                   = 0
close(4)                                = 0
munmap(0x7fa523a25000, 4096)            = 0
access("/volume2/BackupsVMs/PreludeData/.xsitools", F_OK) = 0
open("/volume2/BackupsVMs/PreludeData/.xsitools", O_RDONLY) = 4
open("/tmp/xsi/4002-24322042627078724_edit_tmp", O_WRONLY|O_CREAT|O_APPEND, 0666) = -1 ENOENT (No such file or directory)
stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2910, ...}) = 0
write(1, "2021-10-20T09:46:55 | Error code"..., 1172021-10-20T09:46:55 | Error code 2833 at file common.c, line 2833 | Error description: can't open fd_tmp_f2edit file
) = 117
write(1, "\33[90m---------------------------"..., 119-------------------------------------------------------------------------------------------------------------
) = 119
open("/var/log/xsi/error.log", O_WRONLY|O_CREAT|O_APPEND, 0666) = 5
fstat(5, {st_mode=S_IFREG|0644, st_size=2268, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7fa523a25000
fstat(5, {st_mode=S_IFREG|0644, st_size=2268, ...}) = 0
lseek(5, 2268, SEEK_SET)                = 2268
socket(PF_LOCAL, SOCK_DGRAM, 0)         = 6
fcntl(6, F_SETFD, FD_CLOEXEC)           = 0
connect(6, {sa_family=AF_LOCAL, sun_path="/dev/log"}, 110) = 0
stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2910, ...}) = 0
stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2910, ...}) = 0
stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2910, ...}) = 0
sendto(6, "<27>Oct 20 09:46:55 xsibackup: E"..., 143, MSG_NOSIGNAL, NULL, 0) = 143
close(6)                                = 0
write(5, "2021-10-20T09:46:55 | Error code"..., 117) = 117
close(5)                                = 0
munmap(0x7fa523a25000, 4096)            = 0
stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2910, ...}) = 0
write(1, "2021-10-20T09:46:55 | Error code"..., 1572021-10-20T09:46:55 | Error code 843 at file prune.c, line 843 | Error description: Can't add block count info to: /volume2/BackupsVMs/PreludeData/.xsitools
) = 157
write(1, "\33[90m---------------------------"..., 119-------------------------------------------------------------------------------------------------------------
) = 119
open("/var/log/xsi/error.log", O_WRONLY|O_CREAT|O_APPEND, 0666) = 5
fstat(5, {st_mode=S_IFREG|0644, st_size=2385, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7fa523a25000
fstat(5, {st_mode=S_IFREG|0644, st_size=2385, ...}) = 0
lseek(5, 2385, SEEK_SET)                = 2385
socket(PF_LOCAL, SOCK_DGRAM, 0)         = 6
fcntl(6, F_SETFD, FD_CLOEXEC)           = 0
connect(6, {sa_family=AF_LOCAL, sun_path="/dev/log"}, 110) = 0
stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2910, ...}) = 0
stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2910, ...}) = 0
stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2910, ...}) = 0
sendto(6, "<27>Oct 20 09:46:55 xsibackup: E"..., 183, MSG_NOSIGNAL, NULL, 0) = 183
close(6)                                = 0
write(5, "2021-10-20T09:46:55 | Error code"..., 157) = 157
close(5)                                = 0

Seems like it can't open /tmp/xsi/4002-24322042627078724_edit_tmp. Unfortunately no /tmp/xsi directory ...

thanks,
regards,

Michele

Offline

#6 2021-10-20 08:02:07

admin
Administrator
Registered: 2017-04-21
Posts: 1,821

Re: XSIbackup-DC 1.5.1.1 - error 2516/2833 while pruning on a Synology Box

There must be some previous line in which the target .xsitools file is copied to the /tmp/xsi dir to be edited. It all seems like a permission issue. Are you using the root user?

The /tmp dir should have at least 0770 permissions, normally 0777, there's something wrong in it.

Offline

#7 2021-10-20 08:06:27

michib
Member
Registered: 2020-02-02
Posts: 25

Re: XSIbackup-DC 1.5.1.1 - error 2516/2833 while pruning on a Synology Box

Dear,

I created a xsi subfolder inside /tmp just to see, and it went ok.

read(4, "684f40e5cf6aecefddfa;1048576\nfff"..., 4096) = 4096
read(4, "fffe42df0e15b3e35e40c5fea8e5b697"..., 4096) = 4096
read(4, "7d72e0e;1048576\nffff8c52d0c61322"..., 4096) = 1094
read(4, "", 4096)                       = 0
lseek(4, 0, SEEK_SET)                   = 0
close(4)                                = 0
munmap(0x7f784e80f000, 4096)            = 0
access("/volume2/BackupsVMs/PreludeData/.xsitools", F_OK) = 0
open("/volume2/BackupsVMs/PreludeData/.xsitools", O_RDONLY) = 4
open("/tmp/xsi/5341-24324143065589488_edit_tmp", O_WRONLY|O_CREAT|O_APPEND, 0666) = 5
fstat(5, {st_mode=S_IFREG|0644, st_size=0, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f784e80f000
fstat(5, {st_mode=S_IFREG|0644, st_size=0, ...}) = 0
lseek(5, 0, SEEK_SET)                   = 0
fstat(4, {st_mode=S_IFREG, st_size=64, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f784e80e000
read(4, "Desc: XSITools Repo v 2.0.0\nBsiz"..., 4096) = 64
write(5, "Desc: XSITools Repo v 2.0.0\n", 28) = 28
write(5, "Bsiz: 1048576\n", 14)         = 14
write(5, "Comp: 1\n", 8)                = 8
write(5, "Bcnt: 3881855\n", 14)         = 14
read(4, "", 4096)                       = 0
close(5)                                = 0
munmap(0x7f784e80f000, 4096)            = 0
close(4)                                = 0
munmap(0x7f784e80e000, 4096)            = 0
stat("/tmp/xsi/5341-24324143065589488_edit_tmp", {st_mode=S_IFREG|0644, st_size=64, ...}) = 0
access("/tmp/xsi/5341-24324143065589488_edit_tmp", F_OK) = 0
open("/tmp/xsi/5341-24324143065589488_edit_tmp", O_RDONLY) = 4
open("/volume2/BackupsVMs/PreludeData/.xsitools", O_WRONLY|O_CREAT|O_TRUNC, 0666) = 5
fstat(4, {st_mode=S_IFREG|0644, st_size=64, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f784e80f000
lseek(4, 0, SEEK_SET)                   = 0
read(4, "Desc: XSITools Repo v 2.0.0\nBsiz"..., 65536) = 64
read(4, "", 61440)                      = 0
fstat(5, {st_mode=S_IFREG, st_size=0, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f784e80e000
lseek(5, 0, SEEK_SET)                   = 0
write(5, "Desc: XSITools Repo v 2.0.0\nBsiz"..., 65536) = 65536
ftruncate(5, 64)                        = 0
close(4)                                = 0
munmap(0x7f784e80f000, 4096)            = 0
close(5)                                = 0
munmap(0x7f784e80e000, 4096)            = 0
unlink("/tmp/xsi/5341-24324143065589488_edit_tmp") = 0
write(1, "\33[90m-\33[0m New block count was s"..., 47- New block count was set to: 3881855
) = 47
stat("/volume2/BackupsVMs/PreludeData/Infrastructure-Mail/20210909070000", {st_mode=S_IFDIR, st_size=26, ...}) = 0
stat("/volume2/BackupsVMs/PreludeData/Infrastructure-Mail/20210909070000", {st_mode=S_IFDIR, st_size=26, ...}) = 0
stat("/volume2/BackupsVMs/PreludeData/Infrastructure-Mail/20210909070000", {st_mode=S_IFDIR, st_size=26, ...}) = 0
open("/volume2/BackupsVMs/PreludeData/Infrastructure-Mail/20210909070000", O_RDONLY|O_NONBLOCK|O_DIRECTORY) = 4
fstat(4, {st_mode=S_IFDIR, st_size=26, ...}) = 0
fcntl(4, F_SETFD, FD_CLOEXEC)           = 0
getdents(4, /* 3 entries */, 4096)      = 88

Perms on /tmp seems good:

drwxrwxrwt  19 root root  2500 Oct 20 10:03 tmp

After running it rm the /tmp/xsi folder too...

write(1, "The --prune process finished (1)"..., 33The --prune process finished (1)
) = 33
write(1, "\33[90m---------------------------"..., 119-------------------------------------------------------------------------------------------------------------
) = 119
close(3)                                = 0
munmap(0x7f7866aec000, 4096)            = 0
stat("/tmp/xsi", {st_mode=S_IFDIR|0755, st_size=40, ...}) = 0
stat("/tmp/xsi", {st_mode=S_IFDIR|0755, st_size=40, ...}) = 0
open("/tmp/xsi", O_RDONLY|O_NONBLOCK|O_DIRECTORY) = 3
fstat(3, {st_mode=S_IFDIR|0755, st_size=40, ...}) = 0
fcntl(3, F_SETFD, FD_CLOEXEC)           = 0
getdents(3, /* 2 entries */, 4096)      = 48
getdents(3, /* 0 entries */, 4096)      = 0
rmdir("/tmp/xsi")                       = 0

So maybe it is not able to create /tmp/xsi folder? But why since perms ok?

Thanks,
regards,

Michele

Last edited by michib (2021-10-20 08:07:19)

Offline

#8 2021-10-20 08:52:02

admin
Administrator
Registered: 2017-04-21
Posts: 1,821

Re: XSIbackup-DC 1.5.1.1 - error 2516/2833 while pruning on a Synology Box

We use Synology as well as many other users and it works OK for us. Nonetheless Synology DSM is a propietary OS. It is based in Linux, still they are trying to make it more propietary every day.

It could be a bug in DSM or a broken disk, you are getting an error on an extremely simple open() system call on a folder that should have permissions. The fact that you can open it up manually just shows that whatever is causing the issue does when running the software interactively.

If we were you we would simply change DSM by some full fledged Linux OS. It could very well be some VM sitting on that same Synology volume.

Offline

#9 2021-10-20 09:05:30

michib
Member
Registered: 2020-02-02
Posts: 25

Re: XSIbackup-DC 1.5.1.1 - error 2516/2833 while pruning on a Synology Box

admin wrote:

We use Synology as well as many other users and it works OK for us. Nonetheless Synology DSM is a propietary OS. It is based in Linux, still they are trying to make it more propietary every day.

It could be a bug in DSM or a broken disk, you are getting an error on an extremely simple open() system call on a folder that should have permissions. The fact that you can open it up manually just shows that whatever is causing the issue does when running the software interactively.

If we were you we would simply change DSM by some full fledged Linux OS. It could very well be some VM sitting on that same Synology volume.

Thanks for your reply, I know I can put another Linux VM to do that purge/check jobs every day. But... your conclusions on Synology does not persuade me. I'm using DSM 6.2.4. And moreover I know you also use Synology so the question is: do you want to support it or not?

Anyhow I searched inside xsibackup strace output and I do not find any mkdir('/tmp/xsi').... only the rmdir at the end. It's a little strange, isn't it? As far as I know fopen need to have dirs created to make a new file there.

Obviously I can also do a mkdir on my own to fix it as a W/A but... it's not elegant.

thanks,
regards,
Michele

Offline

#10 2021-10-20 12:15:13

admin
Administrator
Registered: 2017-04-21
Posts: 1,821

Re: XSIbackup-DC 1.5.1.1 - error 2516/2833 while pruning on a Synology Box

We'll investigate this issue further and eventually release a bug fix.

We can try to support Synology as far as it's reasonable to do so, still we can't guarantee compatibility for an OS that is designed with the purpose of hindering the functioning of other software not manufactured by Synology or its partners.

Offline

#11 2021-10-20 12:30:48

admin
Administrator
Registered: 2017-04-21
Posts: 1,821

Re: XSIbackup-DC 1.5.1.1 - error 2516/2833 while pruning on a Synology Box

We sent you a debug version from support. Try it out and let us know if that fixed your issue.

Offline

#12 2021-10-20 13:51:06

admin
Administrator
Registered: 2017-04-21
Posts: 1,821

Re: XSIbackup-DC 1.5.1.1 - error 2516/2833 while pruning on a Synology Box

From a test in an old Synology box in our lab:

|---------------------------------------------------------------------------------|
||-------------------------------------------------------------------------------||
|||   (c)XSIBackup-Free 1.5.1.3: Backup & Replication Software                  |||
|||   (c)33HOPS, Sistemas de Informacion y Redes, S.L. | All Rights Reserved    |||
||-------------------------------------------------------------------------------||
|---------------------------------------------------------------------------------|
                   (c)Daniel J. Garcia Fidalgo | info@33hops.com
|---------------------------------------------------------------------------------|
System Information: Linux, Kernel 3 Major 10 Minor 105 Patch 0
-------------------------------------------------------------------------------------------------------------
PID: 32700, Running job as: root
-------------------------------------------------------------------------------------------------------------
- Pruning '/volume2/backup4/DATACENTER-BACKUP-1M-A/20210211150426'...
- Ordered and unique blocks: 3833, Index depth was set to : 3
- 100.00% | removed 36110 from 36120 blocks in folder | 28.14 GB were liberated
- Deleting blocks from .blocklog file...
- New block count was set to: 3896
- Removed backup folder: /volume2/backup4/DATACENTER-BACKUP-1M-A/20210211150426
The --prune process finished (1)
-------------------------------------------------------------------------------------------------------------
root@NAS01:~# cat /etc/synoinfo.conf | grep -E "(upnpmodelname|udc_check_state)"
upnpmodelname="DS712+"
udc_check_state="6.2.1"

The /temp/xsi dir is configured as the default /tmp dir on (c)XSIBackup, it is sought and created when it doesn't exist on every execution of the software. Thus, it is indeed created on every run when the user that is logged in is root.

Please note that when you login to the DSM command line you don't usually do that as root, thus you must change the user to 'root' to use the software for prunning without any eventual issues.

Offline

Board footer