On Wed, 27 Mar 2019 23:39:56 -0400
backu...@kosowsky.org wrote:
> Gordon Haverland wrote at about 19:34:49 -0700 on Wednesday, March
> 27, 2019:
> > On Tue, 26 Mar 2019 23:21:49 -0400
> > backu...@kosowsky.org wrote:
> >
> > > When running BackupPC_migrateV3toV4, I am getting the following
> > > once on many of my backups
> > > setVarInt botch: got negative argument -2082826800; setting
> > > to 0
> > >
> > > - What could be causing this error?
> > > - How if at all does the above error affect my backup migration?
> > >
> > > Note the error seems to be generated in bpc_attrib.c in the
> > > following subroutine:
> > >
> > > /*
> > > * Write variable-length unsigned integer in 7 bit chunks, LSB
> > > first */
> > > static void setVarInt(uchar **bufPP, uchar *bufEnd, int64 value)
> > > {
> > > uchar *bufP = *bufPP;
> > >
> > > if ( value < 0 ) {
> > > bpc_logErrf("setVarInt botch: got negative argument
> > > %ld; setting to 0\n", (long int)value);
> > > value = 0;
> > > }
> > > do {
> > > uchar c = value & 0x7f;
> > > value >>= 7;
> > > if ( value ) c |= 0x80;
> > > if ( bufP < bufEnd ) {
> > > *bufP++ = c;
> > > } else {
> > > bufP++;
> > > }
> > > } while ( value );
> > > *bufPP = bufP;
> > > }
> >
> > My guess is that long int is a 32 bit quantity. C99 and gcc do
> > seem to have long long int, which is a 64 bit integer (also comes
> > in unsigned).
> >
> > Gord
>
> Interesting...
> So what does this mean in practice?
> - Is there a corruption in my original v3 backup?
> - Is there a bug in the BackupPC_migrateV3toV4?
> - Is my v4 backup now corrupt?
I am just a user of BackupPC, and a beginning one at that. I think
someone on the development side needs to comment on this. Perhaps you
need to submit a bug report?
Gord
_______________________________________________
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/
