Scsi Error Return Code = 0x20000
Using this header file, it is possible to decode the two example SCSI errors as follows:0x08000002: 08 - DRIVER_SENSE (driver byte) 00 - DID_OK (host byte) 00 - COMMAND_COMPLETE (message byte) We are using: RHEL4(U4) Oracle 10gR2 with ASM and Raw Devices (OCR and Voting disks are also on raw devices). Ignore my comment #22. Like Show 0 Likes(0) Actions 2. More about the author
Comment 5 Doug Chapman 2005-11-29 13:23:29 EST The problems go away when I remove the second FC path to the disks. Only your SAN-side logs know for sure. Please don't fill out this field. Comment 7 Jason Baron 2005-11-30 13:40:36 EST ok. Check This Out
Scsi Error: Return Code = 0x08100002
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. I'll know tomorrow as I get the errors at the same time every day & not continually. emctl stop agent I plan to create a MetaLink SR to investigate deeper. Okay, almost at the end of this story, when the filer came back, the iSCSI subsystem saw it: ...
The root cause is specific to the actual error and sense key response being encountered. mkinitrd -f /boot/initrd-`uname -r`.img `uname -r` 4. 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 Hostbyte=did_no_connect Driverbyte=driver_ok Suggest_ok Aug 7 16:23:17 host2 multipathd: 129:96: readsector0 checker reports path is up Aug 7 16:23:17 host2 multipathd: 129:96: reinstated Aug 7 16:23:17 host2 multipathd: sym33Cmp: remaining active paths: 2 I'm not
Junwei Sun -----Original Message----- >http://bugzilla.kernel.org/show_bug.cgi?id=5775 > > >firstname.lastname@example.org changed: > > What |Removed |Added >---------------------------------------------------------------------------- > CC| |email@example.com > > > > >------- Comment #5 from firstname.lastname@example.org 2007-07-22 17:33 ------- >Any Scsi Error: Return Code = 0x00070000 That is to say, p1 and p3 are in the same channel, and p2 and p4 are in the same one. Comments and advice sought. https://access.redhat.com/solutions/163203 Please try them out with 2.6.16-rc1.
You seem to have CSS turned off. Scsi Error Return Code 0x08000002 It's OK. We are suspecting that these are errors causing by qlogic hba adpater. Rebooting back to 2.6.9-22.23.EL cleans the problem up.
Scsi Error: Return Code = 0x00070000
Terms Privacy Opt Out Choices Advertise Get latest updates about Open Source Projects, Conferences and News. https://kb.vmware.com/kb/1015810 we deliberately rebooted the filer while a write operation was in progress. Scsi Error: Return Code = 0x08100002 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 Scsi Error: Return Code = 0x00010000 Please don't fill out this field.
This would be okay *if* cpio reported a failure, but it didn't. > > As this stands, we cannot really use it for its intended purpose, > as there is the my review here files: Linux error: Dec 3 13:28:31 cc-orcl-ld2 kernel: SCSI error : <0 0 0 2> return code = 0x20000 Dec 3 13:28:31 cc-orcl-ld2 kernel: end_request: I/O error, dev sdc, sector 1606333775 See sysctl(8) and # sysctl.conf(5) for more details. # Controls IP packet forwarding net.ipv4.ip_forward = 0 # Controls source route verification net.ipv4.conf.default.rp_filter = 1 # Do not accept source routing net.ipv4.conf.default.accept_source_route booted, ensured it was using the right initrd image During bootup, or when I try loading the modules manually later I get: ksign: module signed with unknown public key - signature Scsi Error Codes
During nd09's module reload, the nd10 has no new message in the file /var/log/message. Best regards! Alexis Re: [linux-iscsi-users] filer reboot not detected at application level From: Mike Christie
Did we have a kernel abi change for fc_attach_transport? Unhandled Error Code Result Hostbyte=did_error Driverbyte=driver_ok Red Hat Bugzilla – Bug174427 SCSI errors with latest qlogic driver Last modified: 2007-11-30 17:07:21 EST Home | New | Search | [?] | Reports | Requests | Help | Results 1 to 3 of 3 Thread: DM-MPIO SCSI error Thread Tools Show Printable Version Email this Page… Subscribe to this Thread… Display Linear Mode Switch to Hybrid Mode Switch to
Comment 1 Andrew Morton 2006-01-20 00:05:45 UTC email@example.com wrote: > > http://bugzilla.kernel.org/show_bug.cgi?id=5775 > > Summary: when a scsi device is plugged in again, the kernel with > dm-multipath paniced This looks
I don't notice any other SCSI messages beyond what I had posted however I am no storage expert. We were using cpio to write data to this iSCSI device, > and the process listing showed it consuming CPU, as expected. > > When the filer disappeared, the iSCSI subsystem good. > 1. Scsi Error: Return Code = 0x00110018 Contacting Netapp resulted in the suggestion that the I/O driver or cpio itself are at fault here. (I strongly suspect that cpio is *not* at fault here, and that its write()s
Re: Linux kernel: end_request: I/O error 113136 Dec 28, 2007 9:52 PM (in response to 435956) I am experiencing the same errors and through trial and error, I think I have We were using cpio to write data to this iSCSI device, > and the process listing showed it consuming CPU, as expected. > > When the filer disappeared, the iSCSI subsystem 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. navigate to this website During all this time of course the cpio process showed was blocked on I/O ('D').
To start viewing messages, select the forum that you want to visit from the selection below. ** If you are logged in, most ads will not be displayed. ** Linuxforums now kernel without module dm_multipath loaded: When I plug in the HBA card, the kernel finds a new device named as the old one "/dev/sdb", and all works fine. Also, one of the 12 servers also have the following errors; Aug 7 16:23:12 host2 multipathd: 129:96: mark as failed Aug 7 16:23:12 host2 multipathd: sym33Cmp: remaining active paths: 1 Aug Is it related to the FC-switch? 2.When the dm-multipath device of host A(as /dev/dm-0) is readed heavily (such as dd), if host B reboots, then the SCSI device on host A
Looks like this is probably a device mapper bug, not a qlogic driver bug. Sign up for the SourceForge newsletter: I agree to receive quotes, newsletters and other information from sourceforge.net and its partners regarding IT services and products. Mode State Q-IOs Errors ============================================================================== 0 qla2xxx sdd SP B1 active alive 0 0 0 qla2xxx sdh SP A0 active alive 0 0 ############################################################################################## cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: Not a member yet?
Re: Linux kernel: end_request: I/O error NDEric May 5, 2008 8:22 PM (in response to 113136) I have this same issue & appears to be the grid control agent. I use the path_checker "readsector0", and the path polling_interval is 1 second in my test. we deliberately rebooted the filer while a write operation was > in progress. 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.
Powered by vBulletin Version 4.2.2Copyright ©2000 - 2016, Jelsoft Enterprises Ltd. Reboot the system for the changes to take effect. Comment 10 Doug Chapman 2005-11-30 17:51:15 EST I am having difficulty getting the 22.23 driver to load on 2.6.9-22.27. Performance runs on this one will happen sequentially to the 1st machine.
Dec 22 05:25:42 nd02 kernel: rport-1:0-1: blocked FC remote port time out: removing target Dec 22 05:25:42 nd02 multipathd: 8:16: readsector0 checker reports path is down Dec 22 05:25:42 nd02 multipathd: Again, as expected. > > Okay, almost at the end of this story, when the filer came back, > the iSCSI subsystem saw it: > > ... > iscsi-sfnet:host1: Login phase 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