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 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 Is there any problem? thanks rk 9621Views Tags: none (add) This content has been marked as final. http://wx2me.com/scsi-error/scsi-error-0x20000.php
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 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 Thanks, David 09-23-2006 #2 jbailey View Profile View Forum Posts Private Message View Articles Just Joined! Comment 9 Doug Chapman 2005-11-30 15:29:56 EST Previous to .24 it worked fine and was using both paths as Active-Active. his comment is here
This may also occur on ext3 if it is using shared storage. But we don't have any concrete information. 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.
We are using: RHEL4(U4) Oracle 10gR2 with ASM and Raw Devices (OCR and Voting disks are also on raw devices). Edit the /etc/modprobe.conf and add the following line (if the line that begins with options qla2xxx already exists, you need to append this option at the end of the line): options Kernel oops when multipath does failback do not exist now. > But other problems exist yet. Hostbyte=did_no_connect Driverbyte=driver_ok Suggest_ok we deliberately rebooted the filer while a write operation was in progress.
More discussions in Generic Linux All PlacesServer & Storage SystemsOracle LinuxGeneric Linux This discussion is archived 4 Replies Latest reply on May 5, 2008 8:22 PM by NDEric Linux kernel: end_request: Scsi Error: Return Code = 0x00070000 and so on ... 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 see this 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
Many thanks! Scsi Error Return Code 0x08000002 Fix: To correctly interpret the RSCN event, it is necessary to add one kernel module option in the modprobe.conf file. Please don't fill out this field. When two controllers work in Active-Standby mode, for example, controller A now is the active one, then, the port p3/p4 is connnected to p1/p2 through a so called internel hub in
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 | Re: Linux kernel: end_request: I/O error 435956 Dec 21, 2007 5:59 PM (in response to TommyReynolds-Oracle) Hi Tommy Thanks for your response. Scsi Error: Return Code = 0x08100002 However, these could really be a bad spot on the SCSI disks. Scsi Error: Return Code = 0x00010000 I'll be opening SR shortly.
Comment 4 Andrew Vasquez 2006-01-24 08:59:00 UTC > I've patched all three patches to the kernel 2.6.16-rc1; > It is better. http://wx2me.com/scsi-error/scsi-error-return-code-0x070e0000.php Looks like this is probably a device mapper bug, not a qlogic driver bug. Specifically it was this patch. 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. Scsi Error Codes
The time now is 11:37 AM. Home | New | Browse | Search | [?] | Reports | Help | NewAccount | Log In [x] | Forgot Password Login: [x] Register Help Remember Me? Rebooting back to 2.6.9-22.23.EL cleans the problem up. have a peek at these guys Do you have any idea how to monitor hba's queue length?
During all this time of course the cpio process showed was blocked on I/O ('D'). Unhandled Error Code Result Hostbyte=did_error Driverbyte=driver_ok The messages continue to occur every once booted every few minutes while idle. Re: Linux kernel: end_request: I/O error TommyReynolds-Oracle Dec 20, 2007 3:44 PM (in response to 435956) These type errors are often produced as a SAN multipath link fails over.
Please don't fill out this field. I will have to look at cpio but when you see this type of message and you are not using something like dm-multipath then the the error has gone above the Comment 6 Anonymous Emailer 2007-07-23 09:00:49 UTC Reply-To: firstname.lastname@example.org Hi bugme-daemon, No, the kernel 220.127.116.11 looks that it works well.Thanks. Scsi Error: Return Code = 0x00110018 Comment 16 Doug Chapman 2005-12-01 14:28:48 EST HP refers to the card as: "PCI-X dual Channel 2Gb Fibre Channel HBA" A6826A I assume qlogic has another name for it as well.
Kernel oops when multipath does failback do not exist now. Join Date Aug 2006 Location McKinney, TX Posts 2 0x2000 SCSI Error Fix This is the fix for this issue (from Red Hat); Environment: EMC SW: PowerPath Environment: OS: Red Hat Best regards! check my blog Any suggestions for testing or possible causes?
Many thanks! It is still a problem, just not a qlogic driver problem. Ok. The HBA is performing it's standard recovery given the actions of the storage -- ABTS for stuck commands and PLOGIs in response to the unexpected LOGOs from the storage during heavy
But if there is no heavy read, no device will lose. 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. 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. 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
if host B reboots more than one time, all SCSI > devices will lose at last. Briefly describe the problem (required): Upload screenshot of ad (required): Select a file, or drag & drop file here. ✔ ✘ Please provide the ad click URL, if possible: Home Browse Environment SUSE Linux Enterprise Server 11SUSE Linux Enterprise Server 10SUSE Linux Enterprise Server 9 Situation Under certain conditions, SCSI errors can be encountered in /var/log/messages. SCSI error : <2 0 0 1> return code = 0x20000 end_request: I/O error, dev sdd, sector 0 Buffer I/O error on device sdd, logical block 0 SCSI error : <2
Basically I'm seeing entries in /var/log/messages similar to; Aug 7 16:31:06 host1 kernel: SCSI error : <1 0 0 70> return code = 0x20000 Aug 7 16:31:06 host1 kernel: end_request: I/O If you have one running, try stopping it and see if the errors disappear. Does this occur with other programs? Comment 12 Mike Christie 2005-11-30 19:12:22 EST You need the transport class module scsi_transport_fc too.
Comment 17 Mike Christie 2005-12-01 14:52:05 EST I must have looked at the commit messages wrong. Aug 7 16:31:06 host1 multipathd: 129:160: mark as failed Aug 7 16:31:06 host1 multipathd: sym34Cmp: remaining active paths: 1 Aug 7 16:31:10 host1 multipathd: 129:160: readsector0 checker reports path is up Junwei Sun -----Original Message----- >http://bugzilla.kernel.org/show_bug.cgi?id=5775 > > >email@example.com changed: > > What |Removed |Added >---------------------------------------------------------------------------- > CC| |firstname.lastname@example.org > > > > >------- Comment #5 from email@example.com 2007-07-22 17:33 ------- >Any 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
Only your SAN-side logs know for sure.