>>>>> On Thu, 26 Mar 2020 23:31:43 +0100, Pierre Bernhardt said: > > Am 26.03.20 um 16:48 schrieb Martin Simmons: > > Looks like a bug to me, but a possible workaround is to limit the size of > > your > Me2. If the short block is correctly identified at writing it should be > repeated > or should be finished on the new disk. In both cases the data on the disks > should > be ok. Only the reading has maybe than a problem. > But if the tail data of the short block is lost, the data on the disks should > be > incomplete
I think the short block should be repeated on the new disk. > 21-Mar 20:23 backup-dir JobId 47704: Using Volume "DISK016" from 'Scratch' > pool. > 21-Mar 20:23 backup-dir JobId 47704: Using Device "DiskStorage2" to write. > 21-Mar 20:23 backup-sd JobId 47704: Wrote label to prelabeled Volume > "DISK016" on File device "DiskStorage2" (/media/baculadisk2) > 22-Mar 07:47 backup-sd JobId 47704: [SI0201] Out of freespace caused End of > Volume "DISK016" at 972406513998 on device "DiskStorage2" > (/media/baculadisk2). Write of 64512 bytes got 57010. > 22-Mar 07:47 backup-sd JobId 47704: End of medium on Volume "DISK016" > Bytes=972,406,513,998 Blocks=15,073,266 at 22-Mar-2020 07:47. > 22-Mar 07:47 backup-sd JobId 47704: OK, this look as expected. > By the way I created a bscan. Here the lines about the disk change: > > > bscan: bscan.c:442-0 Record: SessId=42 SessTim=1584646035 FileIndex=932145 > Stream=23 len=62656 > bscan: bscan.c:442-0 Record: SessId=42 SessTim=1584646035 FileIndex=932145 > Stream=23 len=62336 > bscan: bscan.c:442-0 Record: SessId=42 SessTim=1584646035 FileIndex=932145 > Stream=23 len=61632 > bscan: bscan.c:442-0 Record: SessId=42 SessTim=1584646035 FileIndex=932145 > Stream=23 len=62528 > bscan: bscan.c:442-0 Record: SessId=42 SessTim=1584646035 FileIndex=932145 > Stream=23 len=62672 > 25-Mar 23:27 bscan JobId 0: Error: block.c:682 [SE0208] Volume data error at > 0:0! Short block of 57010 bytes on device "FileTmpVol" (/media/baculadisk2) > discarded. > ... > > Any idea how I can extract the single data für fileindex 932145 from the > disks for comparing? > If the short block is only repeated as whole block on the next disk the > problem could be fixed > by modify the database so the short block will not be read or by truncating > at short block on > the DISK016 (?) You can find the filename for fileindex 932145 by running bscan -r -vv and then do a restore for that filename. __Martin _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
