Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[Veritas\-bu\]\s+sgscan\s+hangs\s+and\s+cannot\s+kill\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[Veritas\-bu\]\s+sgscan\s+hangs\s+and\s+cannot\s+kill\s*$/: 3 ]

Total 3 documents matching your query.

1. [Veritas-bu] sgscan hangs and cannot kill (score: 1): Author: Gary.Seibak AT Metavante DOT com (Gary.Seibak AT Metavante DOT com); Date: Thu, 24 Mar 2005 18:18:33 -0600; Running Solaris 8 and using 9840B tape drives. When I run sgscan it gets to a certain point and stops. I see that sgscan calls scsi_command and it cannot be killed even with kill -9. Anyone ever see; /usr/local/webapp/mharc-adsm.org/html/Veritas-bu/2005-03/msg00382.html (10,986 bytes)
2. [Veritas-bu] sgscan hangs and cannot kill (score: 1): Author: ddunham AT taos DOT com (Darren Dunham); Date: Thu, 24 Mar 2005 16:34:16 -0800 (PST); Often. Signals cannot be delivered to a process that is running in kernel space (as it does during a system call). If the driver is wonky or can't cope with the current situation (flaky drive, bad c; /usr/local/webapp/mharc-adsm.org/html/Veritas-bu/2005-03/msg00383.html (12,024 bytes)
3. [Veritas-bu] sgscan hangs and cannot kill (score: 1): Author: ddunham AT taos DOT com (Darren Dunham); Date: Thu, 24 Mar 2005 17:08:14 -0800 (PST); Look in /etc/path_to_inst for "st" entries. The instance on the entry should correspond to the /dev/rmt/xx number, and the path to the device should correspond to the /devices/... bit you have. -- D; /usr/local/webapp/mharc-adsm.org/html/Veritas-bu/2005-03/msg00384.html (11,281 bytes)

Current List: 1 - 3
Page: [1]