Hello,
i didn't find any solution on forums
i would like to open top by sharing of tape drives between 2 media servers
i understand that reservation conflict is normal behaviour, few times per day or one daily we have error 18 or Control daemon connect or protocol error
on SAN switch is set failover for tape drives
media servers are RedHat with newest kernel and nbu is 7.5.0.7
the tape drives are never down and are working properly
have anybody suggestion?
Mar 6 05:00:05 gcs-amsdc1-nbmed02 kernel: st 1:0:1:0: reservation conflict
Mar 6 05:00:05 gcs-amsdc1-nbmed02 kernel: st 1:0:2:0: reservation conflict
Mar 6 05:00:05 gcs-amsdc1-nbmed02 kernel: st2: Error 18 (driver bt 0x0, host bt 0x0).
Mar 6 05:00:05 gcs-amsdc1-nbmed02 kernel: st 1:0:3:0: reservation conflict
Mar 6 05:00:05 gcs-amsdc1-nbmed02 kernel: st 1:0:3:0: reservation conflict
# more messages | grep "Error 18"
Mar 2 05:00:04 gcs-amsdc1-nbmed02 kernel: st3: Error 18 (driver bt 0x0, host bt 0x0).
Mar 4 05:00:05 gcs-amsdc1-nbmed02 kernel: st0: Error 18 (driver bt 0x0, host bt 0x0).
Mar 4 05:00:05 gcs-amsdc1-nbmed02 kernel: st2: Error 18 (driver bt 0x0, host bt 0x0).
Mar 5 05:00:05 gcs-amsdc1-nbmed02 kernel: st0: Error 18 (driver bt 0x0, host bt 0x0).
Mar 5 05:00:05 gcs-amsdc1-nbmed02 kernel: st1: Error 18 (driver bt 0x0, host bt 0x0).
Mar 6 05:00:05 gcs-amsdc1-nbmed02 kernel: st2: Error 18 (driver bt 0x0, host bt 0x0).
]# more messages | grep DOWN
Mar 2 13:56:33 gcs-amsdc1-nbmed02 tldd[14472]: TLD(1) going to DOWN state, status: Control daemon connect or protocol error
Mar 2 13:56:34 gcs-amsdc1-nbmed02 ltid[14446]: Request for media ID D177L5 is being rejected because mount requests are disabled (reason = robotic daemon going to DOWN state)
Mar 2 13:56:34 gcs-amsdc1-nbmed02 ltid[14446]: Request for media ID D146L5 is being rejected because mount requests are disabled (reason = robotic daemon going to DOWN state)
Mar 2 13:56:34 gcs-amsdc1-nbmed02 tldd[14472]: TLD(1) going to DOWN state, status: Control daemon connect or protocol error
Mar 2 14:00:11 gcs-amsdc1-nbmed02 tldd[14472]: TLD(1) going to DOWN state, status: Control daemon connect or protocol error
Mar 2 14:00:17 gcs-amsdc1-nbmed02 tldd[14472]: TLD(1) going to DOWN state, status: Control daemon connect or protocol error
more messages | grep error
Mar 2 13:56:33 gcs-amsdc1-nbmed02 tldd[14472]: TLD(1) going to DOWN state, status: Control daemon connect or protocol error
Mar 2 13:56:34 gcs-amsdc1-nbmed02 tldd[14472]: TLD(1) going to DOWN state, status: Control daemon connect or protocol error
Mar 2 14:00:11 gcs-amsdc1-nbmed02 tldd[14472]: TLD(1) going to DOWN state, status: Control daemon connect or protocol error
Mar 2 14:00:17 gcs-amsdc1-nbmed02 tldd[14472]: TLD(1) going to DOWN state, status: Control daemon connect or protocol error
Mar 2 14:02:11 gcs-amsdc1-nbmed02 tldd[14472]: TLD(1) unavailable: initialization failed: Control daemon connect or protocol error
Mar 2 14:07:42 gcs-amsdc1-nbmed02 tldd[14472]: TLD(1) unavailable: initialization failed: Control daemon connect or protocol error
Mar 2 14:13:13 gcs-amsdc1-nbmed02 tldd[14472]: TLD(1) unavailable: initialization failed: Control daemon connect or protocol error
Mar 2 14:18:44 gcs-amsdc1-nbmed02 tldd[14472]: TLD(1) unavailable: initialization failed: Control daemon connect or protocol error
Mar 2 14:24:16 gcs-amsdc1-nbmed02 tldd[14472]: TLD(1) unavailable: initialization failed: Control daemon connect or protocol error