Re: [BackupPC-users] bpc_read error messages
No, those are recently added warnings as part of a fix for the case where the pool file is actually smaller than the file size in the attributes. In your case, the file size from the attributes is 18446744073709551613 (64 bit unsigned -3). I'm not sure how it got that way (possibly some corruption of the attribute file for that directory?), but the log message should mean it will get repaired during that backup. Craig On Tuesday, January 30, 2018, infos+backu...@ba-cst.net < infos+backu...@ba-cst.net> wrote: > Hello, > > We are using BPC 4, should be with latest release of every component. > > Not sure if this could mean troubles or some bug, so... > > While looking at a full XferLog, we found several "read past EOF" error > messages, with a huge fileSize (always the same for each error). Here > are two of those (with very short context in case it's useful) : > > same recv .d..t.. rwxr-xr-x 0, 0 4096 usr/portage/dev-php/pecl-http > G bpc_read: read past EOF; readSize = 262500, posn = 0, fileSize = > 18446744073709551613, bufferSize = 8388608 > G bpc_read: read past EOF; readSize = 34398, posn = 262500, fileSize = > 18446744073709551613, bufferSize = 8388608 > new recv >f.st.. rw-r--r-- 0, 0 3070 > usr/portage/dev-php/pecl-http/Manifest > > Are those errors troubles in the making ? They seem to have appeared > after a storage disk upgrade with offline rsync between old and new BPC > data repository. > > Tia, > -- B Consultants > > > -- > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > ___ > 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/ > -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ 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] bpc_read error messages
No, those are recently added warnings as part of a fix for the case where the pool file is actually smaller than the file size in the attributes. In your case, the file size from the attributes is 18446744073709551613 (64 bit unsigned -3). I'm not sure how it got that way (possibly some corruption of the attribute file for that directory?), but the log message should mean it will get repaired during that backup. Craig On Tuesday, January 30, 2018, infos+backu...@ba-cst.net < infos+backu...@ba-cst.net> wrote: > Hello, > > We are using BPC 4, should be with latest release of every component. > > Not sure if this could mean troubles or some bug, so... > > While looking at a full XferLog, we found several "read past EOF" error > messages, with a huge fileSize (always the same for each error). Here > are two of those (with very short context in case it's useful) : > > same recv .d..t.. rwxr-xr-x 0, 0 4096 usr/portage/dev-php/pecl-http > G bpc_read: read past EOF; readSize = 262500, posn = 0, fileSize = > 18446744073709551613, bufferSize = 8388608 > G bpc_read: read past EOF; readSize = 34398, posn = 262500, fileSize = > 18446744073709551613, bufferSize = 8388608 > new recv >f.st.. rw-r--r-- 0, 0 3070 > usr/portage/dev-php/pecl-http/Manifest > > Are those errors troubles in the making ? They seem to have appeared > after a storage disk upgrade with offline rsync between old and new BPC > data repository. > > Tia, > -- B Consultants > > > -- > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > ___ > 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/ > -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ 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] bpc_read error messages
Hello, We are using BPC 4, should be with latest release of every component. Not sure if this could mean troubles or some bug, so... While looking at a full XferLog, we found several "read past EOF" error messages, with a huge fileSize (always the same for each error). Here are two of those (with very short context in case it's useful) : same recv .d..t.. rwxr-xr-x 0, 0 4096 usr/portage/dev-php/pecl-http G bpc_read: read past EOF; readSize = 262500, posn = 0, fileSize = 18446744073709551613, bufferSize = 8388608 G bpc_read: read past EOF; readSize = 34398, posn = 262500, fileSize = 18446744073709551613, bufferSize = 8388608 new recv >f.st.. rw-r--r-- 0, 0 3070 usr/portage/dev-php/pecl-http/Manifest Are those errors troubles in the making ? They seem to have appeared after a storage disk upgrade with offline rsync between old and new BPC data repository. Tia, -- B Consultants -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ 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/