Bug 111782
Summary: | Inquiry information for SCSI device with LUN>0 not correctly parsed or represented | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | David Tonhofer <bughunt> |
Component: | kernel | Assignee: | Arjan van de Ven <arjanv> |
Status: | CLOSED WONTFIX | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 9 | CC: | riel |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-09-30 15:41:44 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
David Tonhofer
2003-12-10 01:45:30 UTC
I have had an unvoluntary reboot this night...great stuff (The server was just sitting there, switched on, in catatonic mode. No lines in the kernel log to indicate what was wrong. Duh!) So here is what /proc/scsi/scsi looks like after reboot: $ cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 06 Lun: 00 Vendor: 8HP Model: C9264CB-VS80 Rev: 503 Type: Sequential-Access ANSI SCSI revision: ffffffff This is looking ok, but high-LUNs have not been scanned (ok I guess), so I do this using a little script (rescan-scsi-bus.sh), and after that: $ cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 06 Lun: 00 Vendor: 8HP Model: C9264CB-VS80 Rev: 503 Type: Sequential-Access ANSI SCSI revision: ffffffff Host: scsi0 Channel: 00 Id: 06 Lun: 01 Vendor: 8HP Model: C9264CB-VS80 Rev: 503 Type: Medium Changer ANSI SCSI revision: ffffffff Hmmm...so this does not look so bad, even though it's NOT what was indicated before reboot. But now: $ mtx status illegal Element Type Code 54 reported $ mt -f /dev/st0 ...never returns Bad news in the kernel log: (scsi0:A:6:0): data overrun detected in Data-in phase. Tag == 0x2. (scsi0:A:6:0): Have seen Data Phase. Length = 56. NumSGs = 1. sg[0] - Addr 0x01bc28000 : Length 56 Ok, so there is definitely something wrong with the bus, I will change the geometry and be back. Changed geometry. Tape autoloader is now exclusively attached to the RedHat 9.0 machine. After a SCSI bus rescan: $ cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 06 Lun: 00 Vendor: HP Model: C9264CB-VS80 Rev: 5032 Type: Sequential-Access ANSI SCSI revision: 02 Host: scsi0 Channel: 00 Id: 06 Lun: 01 Vendor: HP Model: C9264CB-VS80 Rev: 5032 Type: Medium Changer ANSI SCSI revision: 02 ...so this looks better and better, the ANSI SCSI revision now actually makes sense. $ mtx status Storage Changer /dev/changer:1 Drives, 8 Slots ( 0 Import/Export ) Data Transfer Element 0:Full (Storage Element 4 Loaded) Storage Element 1:Full Storage Element 2:Full Storage Element 3:Full Storage Element 4:Empty Storage Element 5:Full Storage Element 6:Full Storage Element 7:Full Storage Element 8:Full $ mt -f /dev/st0 status SCSI 2 tape drive: File number=-1, block number=-1, partition=0. Tape block size 0 bytes. Density code 0x40 (DLT1 40 GB, or Ultrium). Soft error count since last status=0 General status bits on (1010000): ONLINE IM_REP_EN All right! So it looks like I shot myself in the foot by trying to be too clever by half? Thanks for the bug report. However, Red Hat no longer maintains this version of the product. Please upgrade to the latest version and open a new bug if the problem persists. The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, and if you believe this bug is interesting to them, please report the problem in the bug tracker at: http://bugzilla.fedora.us/ |