Cisco Bug: CSCuq55595 - Disks were reported by storages array as "queue depth 30"
Jun 24, 2020
- Cisco Videoscape Distribution Suite Transparent Caching
Known Affected Releases
Symptom: 118 out of 120 volumes are showing as inactive. CE-2 stuck in "starting" state Conditions: During boot, ce-2 connects to iscsi, and starts negotiation with the storage array in order to enumerate available disks. It starts from storage 0 (first), reads information regarding disks in Lun 0 and 1. This went on ok. On negotiation on disk in Lun 3, storage reports "Enabled tagged queuing, queue depth 32" regarding disk 41:0:0:2 (see relevant log line below). This hang the negotiation with storage and the device would stuck at queue depth 32: Apr 30 11:56:12 ce-2 kernel: scsi 41:0:0:2: Direct-Access IBM VirtualDisk 1070 PQ: 0 ANSI: 5 Apr 30 11:56:12 ce-2 kernel: scsi(41:0:0:2): Enabled tagged queuing, queue depth 32. On ce-1 this didn't happened, and all the disks were reported by storages array as "queue depth 30". After boot, when negotiating on same LUN, storage returns correct information "queue depth 30", and negotiation continued to the end. During system boot the CE hang negotiationwith the storage due to wrong queue depth (=32) that was read from the hardware storage, the software expect that the queue depth will be equaled to 30, that cause to the application to hang the negotiation with the storage.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases