Looks like this is probably a device mapper bug, not a qlogic driver bug. The recovery time of host A's disk IO is too long (as about 33 seconds) during host B reboots, where host A and B share their SAN stroage through HBA and Bookmark Email Document Printer Friendly Favorite Rating: Understanding SCSI Error Codes in LinuxThis document (7006510) is provided subject to the disclaimer at the end of this document. Here is the proc output requested too. [root@hpcp1 ~]# more /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 00 Vendor: HP 36.4G Model: MAU3036NC Rev: HPC2 Type: Direct-Access ANSI this content
Jan 23 23:16:47 nd06 kernel: end_request: I/O error, dev sda, sector 401357576 Jan 23 23:16:48 nd06 multipathd: 8:0: mark as failed Jan 23 23:16:48 nd06 multipathd: STOYOU___NetStor_DA9220F0000013158674E00: Entering recovery mode: max_retries=100 copied kernel/drivers/scsi/qla1280.ko and kernel/drivers/scsi/qla2xxx/* from the 2.6.9-22.23 tree to the 2.6.9-22.27 tree. 2. Register If you are a new customer, register now for access to product evaluations and purchasing capabilities. Often times, especially in failover >configurations, a storage box needs a TUR (test-unit-ready) or some >other CDB to force the controller to switch active paths.
Rebooting back to 2.6.9-22.23.EL cleans the problem up. I will try this out first thing tomorrow. All Rights Reserved. Thanks! >> 1. >> I execute the command "dd if=/dev/sda of=/dev/null" in host nd10, after about 1 minutes, >> I do the command "rmmod qla2xxx;modprobe qla2xxx" in host nd09. >> And
Comment 29 John Shakshober 2005-12-12 11:59:59 EST Confirmed -24.1 worked for basic connnectivity to fiber luns [root@perf3 ~]# uname -a Linux perf3.lab.boston.redhat.com 2.6.9-24.1.ELsmp #1 SMP Fri Dec 9 14:27:54 EST 2005 We Acted. Format For Printing -XML -Clone This Bug -Top of page First Last Prev Next This bug is not in your last search results. Scsi Error Return Code 0x08000002 Could you send the rest of the log?
Open Source Communities Subscriptions Downloads Support Cases Account Back Log In Register Red Hat Account Number: Account Details Newsletter and Contact Preferences User Management Account Maintenance My Profile Notifications Help Log Scsi Error: Return Code = 0x00070000 Version-Release number of selected component (if applicable): kernel-2.6.9-22.24.EL How reproducible: Always Steps to Reproduce: 1. Did we have a kernel abi change for fc_attach_transport? https://access.redhat.com/solutions/163203 I'll know tomorrow as I get the errors at the same time every day & not continually.
We are suspecting that these are errors causing by qlogic hba adpater. Does this occur with other programs? Terms Privacy Opt Out Choices Advertise Get latest updates about Open Source Projects, Conferences and News. Reopen it (or create a new bug) if more work on this is needed. (BTW The component wasn't really Storage/DM - someone might like to change it.) Note You need to
Thanks. Need access to an account?If your company has an existing Red Hat account, your organization administrator can grant you access. Scsi Error: Return Code = 0x08100002 Jan 23 23:16:47 nd06 kernel: sd 1:0:2:0: SCSI error: return code = 0x20000 Jan 23 23:16:47 nd06 kernel: end_request: I/O error, dev sdc, sector 401358016 Jan 23 23:16:47 nd06 kernel: end_request: Scsi Error Codes Comment 11 Jason Baron 2005-11-30 17:57:17 EST that's right.
Does this occur with other programs? news It just adds a sysfs attribute. Comment 2 Andrew Vasquez 2006-01-20 16:13:54 UTC I'm trying to lay to rest the final rport/device_model API change requirements for qla2xxx. Yes, we are using multipath but there are no broken disks and we didn't see any errors on SAN logs. Scsi Error: Return Code = 0x00010000
Like Show 0 Likes(0) Actions Go to original post Actions About Oracle Technology Network (OTN)My Oracle Support Community (MOSC)MOS Support PortalAboutModern Marketing BlogRSS FeedPowered byOracle Technology NetworkOracle Communities DirectoryFAQAbout OracleOracle and I am out of the office today and I had pulled a cable to work around this temporarily. Okay, almost at the end of this story, when the filer came back, the iSCSI subsystem saw it: ... have a peek at these guys I don't notice any other SCSI messages beyond what I had posted however I am no storage expert.
This is a 2-node RAC database. Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] Are you running powerpath? You seem to have CSS turned off.
I'm still unclear on the exact toplopgy (not just the >components, but how you've attached those components to the storage. >At least on nd10, I can see the HBAs are coming Steps to reproduce: create the dm multipath device, pull out one HBA card for 1 minute, and plug it in again. Could I get access to the machine? Open Source Communities Subscriptions Downloads Support Cases Account Back Log In Register Red Hat Account Number: Account Details Newsletter and Contact Preferences User Management Account Maintenance My Profile Notifications Help Log
kernel: sd 0:0:0:70: SCSI error: return code = 0x08070002 kernel: sdb: Current: sense key: Aborted Command kernel: Additional sense: Internal target failureThe actual return code and sense key data may be then, presumably after some timeout configured in /etc/iscsi.conf, the iSCSI subsystem started trying to register with the filer again: iscsi-sfnet:host1: Login phase timed out, timeout was set for 77088126 iscsi-sfnet:host1: Connect i'm not sure if this is a dm problem Comment 8 Mike Christie 2005-11-30 14:41:21 EST Can you verify that with the setup that works for pre .24 kernels everything was check my blog During all this time of course the cpio process showed was blocked on I/O ('D').
Best regards! if host B reboots more than one time, all SCSI > devices will lose at last. The logs of file /var/log/messages are: Jan 23 23:16:47 nd06 kernel: qla2300 0000:07:01.1: scsi(1:2:0): Abort command issued -- 137967 2002. If you have any questions, please contact customer service.
Comment 2 Mike Christie 2005-11-29 12:32:42 EST It looks like the larger qlogic update got in at 22.11 here https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=168544 And all that got merged into 22.24 was https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=149294 transport rediscovery. When I do the command "fdisk -l" on nd10, then new messages are added in this file. > >Have you verified the validity of your topology with the storage >vendor? Do we have a kabi change causing a problem here? The version of the qlogic driver is 8.01.02-d2 where the later versions where it doesn't work is 8.01.02-d3.
You can not post a blank message. Please type your message and try again. Log Out Select Your Language English español Deutsch italiano 한국어 français 日本語 português 中文 (中国) русский Customer Portal Products & Services Tools Security Community Infrastructure and Management Cloud Computing Storage JBoss Dec 22 05:25:42 nd02 multipathd: 3600d0230006927de000001618fecaf00: remaining active paths: 1 Dec 22 05:25:43 nd02 multipathd: remove sdb path checker Dec 22 05:25:43 nd02 kernel: Synchronizing SCSI cache for disk sdb: Dec
Jan 23 23:16:47 nd06 kernel: sd 1:0:2:0: scsi: Device offlined - not ready after error recovery Jan 23 23:16:47 nd06 kernel: sd 1:0:2:0: scsi: Device offlined - not ready after error The logs have nothing too useful. I booted 2.6.9-22.27 with the qlogic driver and scsi_transport_fc from 2.6.9-22.23 and it worked OK. Product Security Center Security Updates Security Advisories Red Hat CVE Database Security Labs Keep your systems secure with Red Hat's specialized responses for high-priority security vulnerabilities.