Hi Andreas, thanks for looking into this. Once the SD gets stuck, I see the following in the directory you mentioned:
root@server:/proc/36003/fd# ll total 0 lr-x------ 1 bareos bareos 64 Jan 14 19:15 0 -> /dev/null lr-x------ 1 bareos bareos 64 Jan 14 19:15 1 -> /dev/null lr-x------ 1 bareos bareos 64 Jan 14 19:15 2 -> /dev/null lrwx------ 1 bareos bareos 64 Jan 14 19:15 3 -> 'socket:[110568]' lrwx------ 1 bareos bareos 64 Jan 14 19:15 4 -> 'socket:[117288]' lrwx------ 1 bareos bareos 64 Jan 14 19:15 5 -> /dev/nst0 lrwx------ 1 bareos bareos 64 Jan 14 19:17 6 -> 'socket:[117291]' The SD status out of bconsole is giving: ==== Device status: Device "My-LTO" (/dev/tape/by-id/scsi-1IBM_ULTRIUM-TD1_1391028290-nst) is not open. Device is being initialized. ==== I hope this is useful for you. Many thanks and best regards, Robert Am 14.01.21 um 10:59 schrieb Andreas Rogge:
Hi Folks, could one of you check if the SD kept the device open when this error occurs? i.e. take a look at /proc/<pid of SD>/fd while you're seeing the "device or resource busy" messages. Maybe the SD tries to open a the device while it still has it open (which would be a bug, of course). Best Regards, Andreas
-- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/bareos-users/ffd60068-8052-f981-153f-c923dfbcd903%40yahoo.de.
