Hi,
since last week we changed our openvz-backup CT to kvm to be able to use the new kernel.
The new backup-VM works fine (bareos instead of bacula before) but the LTO-6 Jukebox must be connected to the host. Not an real problem.
But after changing the kernel on the host from 2.6.32-x to 3.10.0-7 I'm unable to mount tapes. Bareos see the tape but can't read the content.
Are there any known changes (e.g. block-size) which can produce such an issue? (we use 1MB-blocksize)
Udo
since last week we changed our openvz-backup CT to kvm to be able to use the new kernel.
The new backup-VM works fine (bareos instead of bacula before) but the LTO-6 Jukebox must be connected to the host. Not an real problem.
But after changing the kernel on the host from 2.6.32-x to 3.10.0-7 I'm unable to mount tapes. Bareos see the tape but can't read the content.
Code:
3305 Autochanger "load slot 9, drive 1", status is OK.
block.c:1004 Read error on fd=4 at file:blk 0:0 on device "LTO6-DRIVE2" (/dev/tape/by-path/pci-0000:0c:00.0-sas-0x5000e11155b61005-lun-0-nst). ERR=Das Gerät oder die Ressource ist belegt.
3902 Cannot mount Volume on Storage Device ""LTO6-DRIVE2" (/dev/tape/by-path/pci-0000:0c:00.0-sas-0x5000e11155b61005-lun-0-nst)" because:
Requested Volume "" on "LTO6-DRIVE2" (/dev/tape/by-path/pci-0000:0c:00.0-sas-0x5000e11155b61005-lun-0-nst) is not a Bareos labeled Volume, because: ERR=block.c:1004 Read error on fd=4 at file:blk 0:0 on device "LTO6-DRIVE2" (/dev/tape/by-path/pci-0000:0c:00.0-sas-0x5000e11155b61005-lun-0-nst). ERR=Das Gerät oder die Ressource ist belegt.
Are there any known changes (e.g. block-size) which can produce such an issue? (we use 1MB-blocksize)
Udo