Knowing the code reasonably well, it's hard to imagine why only those
couple of files would be messed up.

Is there any possibility that the client is returning the wrong
owner/permissions?
What transport protocol are you using?
What is the underlying filesystem?

What if anything is different about those files/directories from
others?
Can you reproduce this when the file is moved elsewhere? (another
directory? another machine?)
Can you use BackupPC_attribPrint to print out the contents of the
relevant raw attrib file?



David Heap via BackupPC-users wrote at about 13:06:48 +0000 on Monday, March 
13, 2023:
 > Hi,
 > 
 > I'm not sure that's correct - files with the same size don't necessarily 
 > have the same content. These are logs that are rotated when they hit a 
 > certain size and this is confirmed by the MD5s (used for deduplication) 
 > differing as seen in the output from BackupPC_ls.
 > 
 > Regardless, the content of the file and the uid/gid attributes should be 
 > separate issues. This was uncovered during a test restore to a different 
 > location.
 > 
 > By way of a little more clarity, I used BackupPC_delete to remove the files 
 > from all backups of this target to maintain consistency in the pool/db. I 
 > then ran BackupPC_nightly 0 255 to try to clear out the no-longer-used files.
 > 
 > So it would seem that something is wrong in the attrib files - thanks for 
 > the pointer, I'll go and have a poke around there to see if I can spot 
 > anything obvious.
 > 
 > Thanks,
 > David
 > 
 > > Yes, those are links to the same size thus same content as the file at the 
 > > top. The only way to check if things are correct is to do a test restore 
 > > to different location and check the ownership of those restored files. 
 > > There are "attrib" files located elsewhere that keep track of the 
 > > ownership and source of the file information. When you manually delete 
 > > files from the pool you corrupt the backuppc data base which could lead to 
 > > future inaccuracies in backups and restores.
 > >
 > > You should read the "How it works" in the backuppc documentation.
 > >
 > > Deduplication is one of the main premises of backuppc.
 > 
 > ________________________________
 > 
 > The Networking People (TNP) Limited. Registered office: Network House, Caton 
 > Rd, Lancaster, LA1 3PE. Registered in England & Wales with company number: 
 > 07667393
 > 
 > This email and any files transmitted with it are confidential and intended 
 > solely for the use of the individual or entity to whom they are addressed. 
 > If you have received this email in error please notify the system manager. 
 > This message contains confidential information and is intended only for the 
 > individual named. If you are not the named addressee you should not 
 > disseminate, distribute or copy this e-mail. Please notify the sender 
 > immediately by e-mail if you have received this e-mail by mistake and delete 
 > this e-mail from your system. If you are not the intended recipient you are 
 > notified that disclosing, copying, distributing or taking any action in 
 > reliance on the contents of this information is strictly prohibited.
 > 
 > 
 > _______________________________________________
 > BackupPC-users mailing list
 > BackupPC-users@lists.sourceforge.net
 > List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
 > Wiki:    https://github.com/backuppc/backuppc/wiki
 > Project: https://backuppc.github.io/backuppc/


_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    https://github.com/backuppc/backuppc/wiki
Project: https://backuppc.github.io/backuppc/

Reply via email to