Looks like a bug to me, but a possible workaround is to limit the size of your
disk volumes (see Maximum Volume Bytes) to avoid filling the disks during the
backup. This will avoid the "short block" when you migrate.
BTW, can you post the log from jobid 47704 as well?
__Martin
> On Wed,
Am 26.03.20 um 14:06 schrieb Josh Fisher:
> On 3/25/2020 3:23 PM, Pierre Bernhardt wrote:
> And what is the Autochanger / Device configurations for the disk storage in
> bacula-sd.conf?
Device {
Name = DiskStorage1
Media Type = Disk
Device Type = File
Archive Device = /media/baculadisk1
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.
On 3/25/2020 3:23 PM, Pierre Bernhardt wrote:
Am 24.03.20 um 22:39 schrieb Pierre Bernhardt:
Today I tried to migrate again the job which uses two disk files.
But now I tried to put both files in one directory (I used my second
bay to mount the DISK017 file) and used a symbolic link:
-rw-rw-r--
