[BUG] Oldest snapshot empty, "No files in this snapshot"

[Cybersmog]

Prerequisites

• I have read the troubleshooting guide

Rclone Pre-flight Checklist (if applicable)

• This issue is NOT related to rclone (skip if not using rclone)
• I have tested rclone listremotes and rclone lsd remote: on the host and they work
• I have verified the rclone config is mounted into the container
• I have restarted the container after config changes

Bug Description

The oldest snapshot reports as being empty. All the other snapshots show content.

Steps to Reproduce

Select oldest snapshot of a Backup

Expected Behavior

The summary indicates that there are >200 files in this snapshot, they should be visible

Zerobyte version / commit

v0.32.4

Deployment Method

Docker Compose

Backup/Repository Context

Im using a remote SFTP backend. All other functionality works as expected as far as I can tell.

Logs / Error Messages

HTTP server response:

So no UI bug I think

Server Logs:

<-- GET /api/v1/repositories/emfmh/snapshots?backupId=c46695f3
<-- GET /api/v1/backups/c46695f3/mirrors/compatibility
<-- GET /api/v1/repositories/emfmh/snapshots/372e715e/files?path=%2Fmydata%2Fpi%2Fpaperless-ngx
--> GET /api/v1/backups/c46695f3/progress 200 86ms
--> GET /api/v1/backups/c46695f3/mirrors/compatibility 200 396ms
<-- GET /api/v1/volumes
--> GET /api/v1/volumes 200 286ms
10:47:19 info SFTP: SSH args: -o LogLevel=ERROR -o BatchMode=yes -o NumberOfPasswordPrompts=0 -o PreferredAuthentications=publickey -o PasswordAuthentication=no -o KbdInteractiveAuthentication=no -o IdentitiesOnly=yes -o ConnectTimeout=10 -o ConnectionAttempts=1 -o ServerAliveInterval=60 -o ServerAliveCountMax=240 -i /tmp/zerobyte-ssh-3018f42ccbfde69a -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null
10:47:19 info SFTP: SSH args: -o LogLevel=ERROR -o BatchMode=yes -o NumberOfPasswordPrompts=0 -o PreferredAuthentications=publickey -o PasswordAuthentication=no -o KbdInteractiveAuthentication=no -o IdentitiesOnly=yes -o ConnectTimeout=10 -o ConnectionAttempts=1 -o ServerAliveInterval=60 -o ServerAliveCountMax=240 -i /tmp/zerobyte-ssh-d2ef64d6d6c95db3 -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null
10:47:19 info SFTP: SSH args: -o LogLevel=ERROR -o BatchMode=yes -o NumberOfPasswordPrompts=0 -o PreferredAuthentications=publickey -o PasswordAuthentication=no -o KbdInteractiveAuthentication=no -o IdentitiesOnly=yes -o ConnectTimeout=10 -o ConnectionAttempts=1 -o ServerAliveInterval=60 -o ServerAliveCountMax=240 -i /tmp/zerobyte-ssh-c2958fb67a15397d -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null
10:47:19 debug Running restic ls with args: --repo sftp:xxx:/zerobyte ls --long --json -o sftp.args=-o LogLevel=ERROR -o BatchMode=yes -o NumberOfPasswordPrompts=0 -o PreferredAuthentications=publickey -o PasswordAuthentication=no -o KbdInteractiveAuthentication=no -o IdentitiesOnly=yes -o ConnectTimeout=10 -o ConnectionAttempts=1 -o ServerAliveInterval=60 -o ServerAliveCountMax=240 -i /tmp/zerobyte-ssh-c2958fb67a15397d -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null --limit-upload 610 -- 372e715e /mydata/pi/paperless-ngx
<-- GET /api/v1/notifications/destinations
--> GET /api/v1/notifications/destinations 200 18ms
<-- GET /api/v1/backups
--> GET /api/v1/backups 200 26ms
<-- GET /api/v1/repositories
--> GET /api/v1/repositories 200 48ms
<-- GET /api/v1/repositories/emfmh/snapshots?backupId=c46695f3
10:47:22 info SFTP: SSH args: -o LogLevel=ERROR -o BatchMode=yes -o NumberOfPasswordPrompts=0 -o PreferredAuthentications=publickey -o PasswordAuthentication=no -o KbdInteractiveAuthentication=no -o IdentitiesOnly=yes -o ConnectTimeout=10 -o ConnectionAttempts=1 -o ServerAliveInterval=60 -o ServerAliveCountMax=240 -i /tmp/zerobyte-ssh-593ff7a49d39e8de -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null
10:47:22 info SFTP: SSH args: -o LogLevel=ERROR -o BatchMode=yes -o NumberOfPasswordPrompts=0 -o PreferredAuthentications=publickey -o PasswordAuthentication=no -o KbdInteractiveAuthentication=no -o IdentitiesOnly=yes -o ConnectTimeout=10 -o ConnectionAttempts=1 -o ServerAliveInterval=60 -o ServerAliveCountMax=240 -i /tmp/zerobyte-ssh-431f50e118e089f5 -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null
10:47:23 debug [Mutex] Released shared lock for repo 56e5965c-517c-4330-80df-0bf75f7f3458: snapshots (held for 4189ms)
--> GET /api/v1/repositories/emfmh/snapshots?backupId=c46695f3 200 4s
10:47:23 debug [Mutex] Released shared lock for repo 56e5965c-517c-4330-80df-0bf75f7f3458: ls:372e715e (held for 4237ms)
--> GET /api/v1/repositories/emfmh/snapshots/372e715e/files?path=%2Fmydata%2Fpi%2Fpaperless-ngx 200 5s
<-- GET /api/v1/backups/c46695f3/progress
--> GET /api/v1/backups/c46695f3/progress 200 25ms

[Cybersmog]

If I remember right, this snapshot used to work some time ago, maybe some update broke it.
Should I test some older version? Does Zerobyte support going back with migrations and all?

[nicotsx]

Hello @Cybersmog thank you for the report. I can confirm the bug. This is not a data loss but rather a zerobyte issue sending the wrong path to lookup in the repo. This is most probably related to a refactor I did recently in the file browser. The weird part is that this happens only on first snapshot. Investigating

[nicotsx]

This should be now fixed for you in v0.33.0 you will see the full path because the snapshot layout doesn't match the current schedule include paths but it should still work the same with restore functionality

[Cybersmog]

Great, thank you!