-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Weird vanished file name #18
Comments
Which version of |
rsync-bpc 3.1.3.0 |
This is internal to The next step is to increase the logging level of |
Somehow it was written to the attrib file. Probably it is a bug but I am afraid we won't be able to reproduce it. What is the proper way to remove the wrong entry from the attrib file? # su -m backuppc -c 'BackupPC_attribPrint /var/db/BackupPC/pc/mx_fsroot/2748/ffsroot/fusr/flocal/flib/attrib_032146d5ac080418877cffc74860ffa4' | grep -A 6 ffsroot
'ffsroot/fusr/flocal/flib/attrib' => {
'compress' => 0,
'digest' => '840ecab5effd0357b41c894e45e01943',
'gid' => 0,
'inode' => 555010,
'mode' => 493,
'mtime' => 1601947653,
'name' => 'ffsroot/fusr/flocal/flib/attrib',
'nlinks' => 0,
'size' => 19,
'type' => 2,
'uid' => 0
},
'libXext.a' => { |
I can't (yet) explain this. The The
The bug is likely in rsync-bpc 3.1.3.0 somewhere. But localizing it to symlinks definitely narrows it down. I'll look at that code to see if there is anyway this could happen. |
On the client host:
|
file has vanished: "/usr/local/lib/ffsroot/fusr/flocal/flib/attrib"
I am quite sure a file (or several files) has really vanished during the backup, but the logged file name is wrong. The reported file and the directory never existed on both client host and BackupPC server.
The text was updated successfully, but these errors were encountered: