date:20200525

Re: [BackupPC-users] Spurious "file doesn't exist" messages... BUG?

2020-05-25 Thread Craig Barratt via BackupPC-users

I'm not sure why you are having problems with bpc-rsync 3.1.2 and
3.1.3-beta0.  Maybe try higher levels of logging and adding -vv to the
remote rsync.  How quickly does it fail?  Is it some ssh-related issue?

I finally was able to get ubuntu to boot on my machine with selinux turned
on in permissive mode, although it's clearly not configured correctly.  I
can see default selinux file attributes with ls -Z.  And I can change them
with chcon or semanage fcontext.  But the actual files I set don't have any
xattr settings.  I assume all those commands are doing is updating files
below /etc/selinux/targeted/contexts/files.  Directly running rsync -X to
copy those files doesn't preserve their selinux attributes.

Anyhow, I separately reconfirmed that a user xattr setting on a regular
file is correctly backed up and restored.

Craig

On Mon, May 25, 2020 at 3:43 PM  wrote:

> Thanks Craig.
> This problem was bothering me for the longest of times... but I always
> assumed it was due to files changing or some other spurious factors...
> But now that I am backing up against fixed snapshots, it has become
> easier to one-by-one track down unexpected bugs & error messages...
>
> The only remaining issue I see now is with SELinux extended attributes
> :)
>
> Plus, the challenges with hangs on bpc-rsyn 3.1.2 and 3.1.3-beta0
>
> Craig Barratt via BackupPC-users wrote at about 13:08:31 -0700 on Monday,
> May 25, 2020:
>  > Jeff,
>  >
>  > Thanks for figuring that out.  I pushed a fix
>  > <
> https://github.com/backuppc/rsync-bpc/commit/96e890fc3e5bb53f6618bd8650e8400f355b243a
> >
>  > so the warning doesn't get printed on zero-length files.
>  >
>  > Craig
>  >
>  > On Mon, May 25, 2020 at 8:08 AM  wrote:
>  >
>  > > Presumably the problem is in rsync-bpc: bpc_sysCalls.c
>  > >
>  > > int bpc_sysCall_checkFileMatch(char *fileName, char *tmpName, struct
>  > > file_struct *rsyncFile,
>  > >char *file_sum, off_t fileSize)
>  > > {
>  > > bpc_attrib_file *fileOrig, *file;
>  > > char poolPath[BPC_MAXPATHLEN];
>  > >
>  > > if ( !(fileOrig = bpc_attribCache_getFile(&acNew, fileName, 0,
> 0)) ) {
>  > > /*
>  > >  * Hmmm.  The file doesn't exist, but we got deltas
> suggesting the
>  > > file is
>  > >  * unchanged.  So that means the generator found a matching
> pool
>  > > file.
>  > >  * Let's try the same thing.
>  > >  */
>  > > if ( bpc_sysCall_poolFileCheck(fileName, rsyncFile)
>  > > || !(fileOrig = bpc_attribCache_getFile(&acNew,
> fileName,
>  > > 0, 0)) ) {
>  > > bpc_logErrf("bpc_sysCall_checkFileMatch(%s): file doesn't
>  > > exist\n", fileName);
>  > > return -1;
>  > > }
>  > > }
>  > > ...
>  > >
>  > > But the zero length file (with md5sum
>  > > d41d8cd98f00b204e9800998ecf8427e) is not in the pool.
>  > >
>  > > Presumably, one should add a check to eliminate...
>  > >
>  > > backu...@kosowsky.org wrote at about 10:36:55 -0400 on Monday, May
> 25,
>  > > 2020:
>  > >  > Seems like these are all the zero length files...
>  > >  > Could it be that backuppc is checking for file length rather than
> file
>  > > existence???
>  > >  >
>  > >  >
>  > >  > Note: when I delete the backup and run it again, the *exact* same
>  > >  > "file doesn't exist' errors reappears (even though a new btrfs
> snapshot
>  > >  > has been created).  So I am pretty sure it is not a filesystem
> issue
>  > >  > but rather likely a bug in backuppc...
>  > >  >
>  > >  >
>  > >  > backu...@kosowsky.org wrote at about 10:00:31 -0400 on Monday,
> May 25,
>  > > 2020:
>  > >  >  > I am still occasionally but not at all consistently getting
> errors
>  > > of form:
>  > >  >  >
>  > >
> Rbpc_sysCall_checkFileMatch(var/lib/spamassassin/3.004002/updates_spamassassin_org/STATISTICS-set3-72_scores.cf.txt):
>  > > file doesn't exist
>  > >  >  >
>  > >  >  > Here is some background:
>  > >  >  > - Only seems to occur on full backups
>  > >  >  > - These messages correspond to files that have changed or been
> added
>  > > since the previous backup
>  > >  >  > - However, they only occur on some incrementals and only for a
> small
>  > > subset of the changed files, even when they do occur
>  > >  >  > - The files are still backed up properly
>  > >  >  > - The files never 'vanished' or changed since I am using
> read-only
>  > > btrfs snapshots
>  > >  >  > - My system is rock-solid and I have not had any other file
> system
>  > > troubles
>  > >  >  >
>  > >  >  > Is this really an error?
>  > >  >  > What is causing it?
>  > >  >  > Why does it happen seemingly randomly?
>  > >  >  >
>  > >  >  >
>  > >  >  > ___
>  > >  >  > BackupPC-users mailing list
>  > >  >  > BackupPC-users@lists.sourceforge.net
>  > >  >  > List:
> https://lists.sourceforge.net/lists/listinfo/backuppc-users
>  > >  >  > Wiki:http://backuppc.wiki.sourceforge.net
>  > >  >  >

Re: [BackupPC-users] Spurious "file doesn't exist" messages... BUG?

2020-05-25 Thread backuppc

Thanks Craig.
This problem was bothering me for the longest of times... but I always
assumed it was due to files changing or some other spurious factors...
But now that I am backing up against fixed snapshots, it has become
easier to one-by-one track down unexpected bugs & error messages...

The only remaining issue I see now is with SELinux extended attributes
:)

Plus, the challenges with hangs on bpc-rsyn 3.1.2 and 3.1.3-beta0

Craig Barratt via BackupPC-users wrote at about 13:08:31 -0700 on Monday, May 
25, 2020:
 > Jeff,
 > 
 > Thanks for figuring that out.  I pushed a fix
 > 
 > so the warning doesn't get printed on zero-length files.
 > 
 > Craig
 > 
 > On Mon, May 25, 2020 at 8:08 AM  wrote:
 > 
 > > Presumably the problem is in rsync-bpc: bpc_sysCalls.c
 > >
 > > int bpc_sysCall_checkFileMatch(char *fileName, char *tmpName, struct
 > > file_struct *rsyncFile,
 > >char *file_sum, off_t fileSize)
 > > {
 > > bpc_attrib_file *fileOrig, *file;
 > > char poolPath[BPC_MAXPATHLEN];
 > >
 > > if ( !(fileOrig = bpc_attribCache_getFile(&acNew, fileName, 0, 0)) ) {
 > > /*
 > >  * Hmmm.  The file doesn't exist, but we got deltas suggesting the
 > > file is
 > >  * unchanged.  So that means the generator found a matching pool
 > > file.
 > >  * Let's try the same thing.
 > >  */
 > > if ( bpc_sysCall_poolFileCheck(fileName, rsyncFile)
 > > || !(fileOrig = bpc_attribCache_getFile(&acNew, fileName,
 > > 0, 0)) ) {
 > > bpc_logErrf("bpc_sysCall_checkFileMatch(%s): file doesn't
 > > exist\n", fileName);
 > > return -1;
 > > }
 > > }
 > > ...
 > >
 > > But the zero length file (with md5sum
 > > d41d8cd98f00b204e9800998ecf8427e) is not in the pool.
 > >
 > > Presumably, one should add a check to eliminate...
 > >
 > > backu...@kosowsky.org wrote at about 10:36:55 -0400 on Monday, May 25,
 > > 2020:
 > >  > Seems like these are all the zero length files...
 > >  > Could it be that backuppc is checking for file length rather than file
 > > existence???
 > >  >
 > >  >
 > >  > Note: when I delete the backup and run it again, the *exact* same
 > >  > "file doesn't exist' errors reappears (even though a new btrfs snapshot
 > >  > has been created).  So I am pretty sure it is not a filesystem issue
 > >  > but rather likely a bug in backuppc...
 > >  >
 > >  >
 > >  > backu...@kosowsky.org wrote at about 10:00:31 -0400 on Monday, May 25,
 > > 2020:
 > >  >  > I am still occasionally but not at all consistently getting errors
 > > of form:
 > >  >  >
 > >  
 > > Rbpc_sysCall_checkFileMatch(var/lib/spamassassin/3.004002/updates_spamassassin_org/STATISTICS-set3-72_scores.cf.txt):
 > > file doesn't exist
 > >  >  >
 > >  >  > Here is some background:
 > >  >  > - Only seems to occur on full backups
 > >  >  > - These messages correspond to files that have changed or been added
 > > since the previous backup
 > >  >  > - However, they only occur on some incrementals and only for a small
 > > subset of the changed files, even when they do occur
 > >  >  > - The files are still backed up properly
 > >  >  > - The files never 'vanished' or changed since I am using read-only
 > > btrfs snapshots
 > >  >  > - My system is rock-solid and I have not had any other file system
 > > troubles
 > >  >  >
 > >  >  > Is this really an error?
 > >  >  > What is causing it?
 > >  >  > Why does it happen seemingly randomly?
 > >  >  >
 > >  >  >
 > >  >  > ___
 > >  >  > BackupPC-users mailing list
 > >  >  > BackupPC-users@lists.sourceforge.net
 > >  >  > List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
 > >  >  > Wiki:http://backuppc.wiki.sourceforge.net
 > >  >  > Project: http://backuppc.sourceforge.net/
 > >  >
 > >  >
 > >  > ___
 > >  > BackupPC-users mailing list
 > >  > BackupPC-users@lists.sourceforge.net
 > >  > List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
 > >  > Wiki:http://backuppc.wiki.sourceforge.net
 > >  > Project: http://backuppc.sourceforge.net/
 > >
 > >
 > > ___
 > > BackupPC-users mailing list
 > > BackupPC-users@lists.sourceforge.net
 > > List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
 > > Wiki:http://backuppc.wiki.sourceforge.net
 > > Project: http://backuppc.sourceforge.net/
 > >
 > ___
 > BackupPC-users mailing list
 > BackupPC-users@lists.sourceforge.net
 > List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
 > Wiki:http://backuppc.wiki.sourceforge.net
 > Project: http://backuppc.sourceforge.net/


___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List

Re: [BackupPC-users] Spurious "file doesn't exist" messages... BUG?

2020-05-25 Thread Craig Barratt via BackupPC-users

Jeff,

Thanks for figuring that out.  I pushed a fix

so the warning doesn't get printed on zero-length files.

Craig

On Mon, May 25, 2020 at 8:08 AM  wrote:

> Presumably the problem is in rsync-bpc: bpc_sysCalls.c
>
> int bpc_sysCall_checkFileMatch(char *fileName, char *tmpName, struct
> file_struct *rsyncFile,
>char *file_sum, off_t fileSize)
> {
> bpc_attrib_file *fileOrig, *file;
> char poolPath[BPC_MAXPATHLEN];
>
> if ( !(fileOrig = bpc_attribCache_getFile(&acNew, fileName, 0, 0)) ) {
> /*
>  * Hmmm.  The file doesn't exist, but we got deltas suggesting the
> file is
>  * unchanged.  So that means the generator found a matching pool
> file.
>  * Let's try the same thing.
>  */
> if ( bpc_sysCall_poolFileCheck(fileName, rsyncFile)
> || !(fileOrig = bpc_attribCache_getFile(&acNew, fileName,
> 0, 0)) ) {
> bpc_logErrf("bpc_sysCall_checkFileMatch(%s): file doesn't
> exist\n", fileName);
> return -1;
> }
> }
> ...
>
> But the zero length file (with md5sum
> d41d8cd98f00b204e9800998ecf8427e) is not in the pool.
>
> Presumably, one should add a check to eliminate...
>
> backu...@kosowsky.org wrote at about 10:36:55 -0400 on Monday, May 25,
> 2020:
>  > Seems like these are all the zero length files...
>  > Could it be that backuppc is checking for file length rather than file
> existence???
>  >
>  >
>  > Note: when I delete the backup and run it again, the *exact* same
>  > "file doesn't exist' errors reappears (even though a new btrfs snapshot
>  > has been created).  So I am pretty sure it is not a filesystem issue
>  > but rather likely a bug in backuppc...
>  >
>  >
>  > backu...@kosowsky.org wrote at about 10:00:31 -0400 on Monday, May 25,
> 2020:
>  >  > I am still occasionally but not at all consistently getting errors
> of form:
>  >  >
>  
> Rbpc_sysCall_checkFileMatch(var/lib/spamassassin/3.004002/updates_spamassassin_org/STATISTICS-set3-72_scores.cf.txt):
> file doesn't exist
>  >  >
>  >  > Here is some background:
>  >  > - Only seems to occur on full backups
>  >  > - These messages correspond to files that have changed or been added
> since the previous backup
>  >  > - However, they only occur on some incrementals and only for a small
> subset of the changed files, even when they do occur
>  >  > - The files are still backed up properly
>  >  > - The files never 'vanished' or changed since I am using read-only
> btrfs snapshots
>  >  > - My system is rock-solid and I have not had any other file system
> troubles
>  >  >
>  >  > Is this really an error?
>  >  > What is causing it?
>  >  > Why does it happen seemingly randomly?
>  >  >
>  >  >
>  >  > ___
>  >  > BackupPC-users mailing list
>  >  > BackupPC-users@lists.sourceforge.net
>  >  > List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
>  >  > Wiki:http://backuppc.wiki.sourceforge.net
>  >  > Project: http://backuppc.sourceforge.net/
>  >
>  >
>  > ___
>  > BackupPC-users mailing list
>  > BackupPC-users@lists.sourceforge.net
>  > List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
>  > Wiki:http://backuppc.wiki.sourceforge.net
>  > Project: http://backuppc.sourceforge.net/
>
>
> ___
> BackupPC-users mailing list
> BackupPC-users@lists.sourceforge.net
> List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
> Wiki:http://backuppc.wiki.sourceforge.net
> Project: http://backuppc.sourceforge.net/
>
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

Re: [BackupPC-users] Spurious "file doesn't exist" messages... BUG?

2020-05-25 Thread backuppc

Presumably the problem is in rsync-bpc: bpc_sysCalls.c

int bpc_sysCall_checkFileMatch(char *fileName, char *tmpName, struct 
file_struct *rsyncFile,
   char *file_sum, off_t fileSize)
{
bpc_attrib_file *fileOrig, *file;
char poolPath[BPC_MAXPATHLEN];

if ( !(fileOrig = bpc_attribCache_getFile(&acNew, fileName, 0, 0)) ) {
/*
 * Hmmm.  The file doesn't exist, but we got deltas suggesting the file 
is
 * unchanged.  So that means the generator found a matching pool file.
 * Let's try the same thing.
 */
if ( bpc_sysCall_poolFileCheck(fileName, rsyncFile)
|| !(fileOrig = bpc_attribCache_getFile(&acNew, fileName, 0, 
0)) ) { 
bpc_logErrf("bpc_sysCall_checkFileMatch(%s): file doesn't exist\n", 
fileName);
return -1;
}
}
...

But the zero length file (with md5sum
d41d8cd98f00b204e9800998ecf8427e) is not in the pool.

Presumably, one should add a check to eliminate...

backu...@kosowsky.org wrote at about 10:36:55 -0400 on Monday, May 25, 2020:
 > Seems like these are all the zero length files...
 > Could it be that backuppc is checking for file length rather than file 
 > existence???
 > 
 > 
 > Note: when I delete the backup and run it again, the *exact* same
 > "file doesn't exist' errors reappears (even though a new btrfs snapshot
 > has been created).  So I am pretty sure it is not a filesystem issue
 > but rather likely a bug in backuppc...
 > 
 > 
 > backu...@kosowsky.org wrote at about 10:00:31 -0400 on Monday, May 25, 2020:
 >  > I am still occasionally but not at all consistently getting errors of 
 > form:
 >  > 
 > Rbpc_sysCall_checkFileMatch(var/lib/spamassassin/3.004002/updates_spamassassin_org/STATISTICS-set3-72_scores.cf.txt):
 >  file doesn't exist
 >  > 
 >  > Here is some background:
 >  > - Only seems to occur on full backups
 >  > - These messages correspond to files that have changed or been added 
 > since the previous backup
 >  > - However, they only occur on some incrementals and only for a small 
 > subset of the changed files, even when they do occur
 >  > - The files are still backed up properly
 >  > - The files never 'vanished' or changed since I am using read-only btrfs 
 > snapshots
 >  > - My system is rock-solid and I have not had any other file system 
 > troubles
 >  > 
 >  > Is this really an error?
 >  > What is causing it?
 >  > Why does it happen seemingly randomly?
 >  > 
 >  > 
 >  > ___
 >  > BackupPC-users mailing list
 >  > BackupPC-users@lists.sourceforge.net
 >  > List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
 >  > Wiki:http://backuppc.wiki.sourceforge.net
 >  > Project: http://backuppc.sourceforge.net/
 > 
 > 
 > ___
 > BackupPC-users mailing list
 > BackupPC-users@lists.sourceforge.net
 > List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
 > Wiki:http://backuppc.wiki.sourceforge.net
 > Project: http://backuppc.sourceforge.net/


___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

Re: [BackupPC-users] Spurious "file doesn't exist" messages... BUG?

2020-05-25 Thread backuppc

Seems like these are all the zero length files...
Could it be that backuppc is checking for file length rather than file 
existence???


Note: when I delete the backup and run it again, the *exact* same
"file doesn't exist' errors reappears (even though a new btrfs snapshot
has been created).  So I am pretty sure it is not a filesystem issue
but rather likely a bug in backuppc...


backu...@kosowsky.org wrote at about 10:00:31 -0400 on Monday, May 25, 2020:
 > I am still occasionally but not at all consistently getting errors of form:
 > 
 > Rbpc_sysCall_checkFileMatch(var/lib/spamassassin/3.004002/updates_spamassassin_org/STATISTICS-set3-72_scores.cf.txt):
 >  file doesn't exist
 > 
 > Here is some background:
 > - Only seems to occur on full backups
 > - These messages correspond to files that have changed or been added since 
 > the previous backup
 > - However, they only occur on some incrementals and only for a small subset 
 > of the changed files, even when they do occur
 > - The files are still backed up properly
 > - The files never 'vanished' or changed since I am using read-only btrfs 
 > snapshots
 > - My system is rock-solid and I have not had any other file system troubles
 > 
 > Is this really an error?
 > What is causing it?
 > Why does it happen seemingly randomly?
 > 
 > 
 > ___
 > BackupPC-users mailing list
 > BackupPC-users@lists.sourceforge.net
 > List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
 > Wiki:http://backuppc.wiki.sourceforge.net
 > Project: http://backuppc.sourceforge.net/


___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

[BackupPC-users] Spurious "file doesn't exist" messages... BUG?

2020-05-25 Thread backuppc

I am still occasionally but not at all consistently getting errors of form:

Rbpc_sysCall_checkFileMatch(var/lib/spamassassin/3.004002/updates_spamassassin_org/STATISTICS-set3-72_scores.cf.txt):
 file doesn't exist

Here is some background:
- Only seems to occur on full backups
- These messages correspond to files that have changed or been added since the 
previous backup
- However, they only occur on some incrementals and only for a small subset of 
the changed files, even when they do occur
- The files are still backed up properly
- The files never 'vanished' or changed since I am using read-only btrfs 
snapshots
- My system is rock-solid and I have not had any other file system troubles

Is this really an error?
What is causing it?
Why does it happen seemingly randomly?


___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

Re: [BackupPC-users] Problems with latest rsync-bpc 3.1.3 - zlib??

2020-05-25 Thread backuppc

Something is really weird here...
I could have sworn that 3.1.2.1 worked fine last night...
But when I tried it again this morning it hanged.
I'm pretty sure the same thing happened with 3.1.3.beta0.

Restoring to 3.0.9.14 worked fined...

Nothing else changed on my system...

I am at a loss to explain this...

Craig Barratt via BackupPC-users wrote at about 21:13:59 -0700 on Sunday, May 
24, 2020:
 > Thanks for the updates.  Yes, rsync's included zlib isn't compatible with
 > system zlib.  However, since you are not using the -z option, I don't think
 > that's the issue.
 > 
 > Can you try rsync-bpc 3.1.2.1?  It has more testing than 3.1.3.beta0.
 > 
 > Craig
 > 
 > On Sun, May 24, 2020 at 7:43 PM  wrote:
 > 
 > > Upgrading to the latest rsync-bpc 3.1.3 fixed the problem with
 > > specials.
 > > And restores all seemed to work last night, until I tried dumps today.
 > >
 > > Now all my scheduled backups fail with error message:
 > > rsync error: error in rsync protocol data stream (code 12) at
 > > io.c(226) [Receiver=3.1.3.beta0]
 > >
 > > Also, when I run BackupPC_dump, it hangs at the beginning:
 > >   Running: /usr/bin/rsync_bpc --bpc-top-dir /var/lib/backuppc
 > > --bpc-host-name testmachine --bpc-share-name /usr/local/bin --bpc-bkup-num
 > > 0 --bpc-bkup-comp 3 --bpc-bkup-prevnum -1 --bpc-bkup-prevcomp -1
 > > --bpc-bkup-inode0 2 --bpc-attrib-new --bpc-log-level 6 -e /usr/bin/sudo\ -h
 > > --rsync-path=/usr/bin/rsync --super --recursive --protect-args
 > > --numeric-ids --perms --owner --group -D --times --links --hard-links
 > > --delete --delete-excluded --one-file-system --partial --log-format=log:\
 > > %o\ %i\ %B\ %8U,%8G\ %9l\ %f%L --stats --checksum --acls --xattrs
 > > --timeout=72000 myhost:/usr/local/bin/ /
 > >   full backup started for directory /usr/local/bin
 > >   started full dump, share=/usr/local/bin
 > >   Xfer PIDs are now 7793
 > >   xferPids 7793
 > >   This is the rsync child about to exec /usr/bin/rsync_bpc
 > >   cmdExecOrEval: about to exec /usr/bin/rsync_bpc --bpc-top-dir
 > > /var/lib/backuppc --bpc-host-name testmachine --bpc-share-name
 > > /usr/local/bin --bpc-bkup-num 0 --bpc-bkup-comp 3 --bpc-bkup-prevnum -1
 > > --bpc-bkup-prevcomp -1 --bpc-bkup-inode0 2 --bpc-attrib-new --bpc-log-level
 > > 6 -e /usr/bin/sudo\ -h --rsync-path=/usr/bin/rsync --super --recursive
 > > --protect-args --numeric-ids --perms --owner --group -D --times --links
 > > --hard-links --delete --delete-excluded --one-file-system --partial
 > > --log-format=log:\ %o\ %i\ %B\ %8U,%8G\ %9l\ %f%L --stats --checksum --acls
 > > --xattrs --timeout=72000 myhost:/usr/local/bin/ /
 > > bpc_path_create(/var/lib/backuppc/pc/testmachine/0)
 > >   bpc_attrib_backwardCompat: WriteOldStyleAttribFile = 0,
 > >   KeepOldAttribFiles = 0
 > >
 > > This problem resolves when I downgrade back to rsync-bpc 3.0.9.
 > >
 > > Googling suggest this might have something to do with internal
 > > vs. external zlib.h
 > >
 > > I tried configuring with --with-included-zlib=yes (default) and =no.
 > > But both had the same error.
 > >
 > > Note that when =yes, in order to compile, I had to change:
 > >  #include  --> #include "zlib/zlib.h"
 > > in token.c (and also changed for consistency in batch.c and options.c)
 > > since the symbol Z_INSERT_ONLY was not defined in my /usr/include/zlib.h
 > >
 > > Any thoughts on what I need to do to make this work?
 > >
 > >
 > > ___
 > > BackupPC-users mailing list
 > > BackupPC-users@lists.sourceforge.net
 > > List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
 > > Wiki:http://backuppc.wiki.sourceforge.net
 > > Project: http://backuppc.sourceforge.net/
 > >
 > ___
 > BackupPC-users mailing list
 > BackupPC-users@lists.sourceforge.net
 > List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
 > Wiki:http://backuppc.wiki.sourceforge.net
 > Project: http://backuppc.sourceforge.net/


___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

Re: [BackupPC-users] Spurious "file doesn't exist" messages... BUG?

Re: [BackupPC-users] Spurious "file doesn't exist" messages... BUG?

Re: [BackupPC-users] Spurious "file doesn't exist" messages... BUG?

Re: [BackupPC-users] Spurious "file doesn't exist" messages... BUG?

Re: [BackupPC-users] Spurious "file doesn't exist" messages... BUG?

[BackupPC-users] Spurious "file doesn't exist" messages... BUG?

Re: [BackupPC-users] Problems with latest rsync-bpc 3.1.3 - zlib??

7 matches

Site Navigation

Mail list logo

Footer information