On Mar 17, 5:06 pm, Mike Christie <micha...@cs.wisc.edu> wrote:
> bigcatxjs wrote:
> > Thanks Mike...
>
> > On Mar 13, 8:45 pm, Mike Christie <micha...@cs.wisc.edu> wrote:
> >> bigcatxjs wrote:
> >>>> At these times is there lots of disk IO? Is there anything in the target
> >>>> logs?
> >>> It is fair to say that all these volumes take a heavy hit, in terms of
> >>> I/O.  Each host (excluding the RHEL 5.3. test host) run two Oracle
> >>> databases, of which some have intra-database replication (Oracle
> >>> Streams) enabled.  The issue on the RHEL 5.2 host occures every 10
> >>> secs or so during Office Hours when it is being utilised.
> >> Do you mean every 10 seconds you see the conn error then conn operation
> >> messages? That sounds like the nop bug in 5.2.
>
> > Yes - this is occuring on the RHEL 5.2 host.
>
> Ok then upgrading to 5.3 should help.
>
>
>
> > I have applied these changes just now.  Thanks.  Received an error
> > logging back into iscsi;
>
> You mean the iferror?
>
>
>
> > Mar 17 12:40:47 MYHOST53 iscsid: received iferror -38
>
> You can ignore this. It just means the userspace tools wanted to set
> value in the kernel but could not because the kernel did not support it.
> The userspace tools should then do it in userspace instead. If it is
> something that the tools cannot work around then it will fail the operation.

Hi,
We have encountered this error below.  This is the first time I have
seen this before;


Mar 17 12:40:47 MYHOST53 kernel:   Vendor: DataCore  Model:
SANmelody         Rev: DCS
Mar 17 12:40:47 MYHOST53 kernel:   Type:   Direct-
Access                      ANSI SCSI revision: 04
Mar 17 12:40:47 MYHOST53 kernel: SCSI device sdd: 41943040 512-byte
hdwr sectors (21475 MB)
Mar 17 12:40:47 MYHOST53 kernel: sdd: Write Protect is off
Mar 17 12:40:47 MYHOST53 kernel: SCSI device sdd: drive cache: write
back w/ FUA
Mar 17 12:40:47 MYHOST53 kernel: SCSI device sdd: 41943040 512-byte
hdwr sectors (21475 MB)
Mar 17 12:40:47 MYHOST53 kernel: sdd: Write Protect is off
Mar 17 12:40:47 MYHOST53 kernel: SCSI device sdd: drive cache: write
back w/ FUA
Mar 17 12:40:47 MYHOST53 kernel:  sdd: sdd1
Mar 17 12:40:47 MYHOST53 kernel: sd 5:0:0:0: Attached scsi disk sdd
Mar 17 12:40:47 MYHOST53 kernel: sd 5:0:0:0: Attached scsi generic sg2
type 0
Mar 17 12:40:47 MYHOST53 iscsid: received iferror -38
Mar 17 18:21:39 MYHOST53 last message repeated 20 times
Mar 17 18:27:59 MYHOST53 kernel: scsi 2:0:0:0: rejecting I/O to dead
device
Mar 17 18:28:04 MYHOST53 kernel: scsi 2:0:0:0: rejecting I/O to dead
device
Mar 17 18:28:04 MYHOST53 kernel: journal_bmap: journal block not found
at offset 2616 on sdc1
Mar 17 18:28:04 MYHOST53 kernel: Aborting journal on device sdc1.
Mar 17 18:28:04 MYHOST53 kernel: scsi 2:0:0:0: rejecting I/O to dead
device
Mar 17 18:28:04 MYHOST53 kernel: Buffer I/O error on device sdc1,
logical block 1545
Mar 17 18:28:04 MYHOST53 kernel: lost page write due to I/O error on
sdc1
Mar 17 23:03:40 MYHOST53 kernel:  connection4:0: iscsi: detected conn
error (1011)
Mar 17 23:03:41 MYHOST53 iscsid: Kernel reported iSCSI connection 4:0
error (1011) state (3)
Mar 17 23:03:44 MYHOST53 iscsid: received iferror -38
Mar 17 23:03:44 MYHOST53 last message repeated 2 times
Mar 17 23:03:44 MYHOST53 iscsid: connection4:0 is operational after
recovery (1 attempts)
Mar 17 23:46:17 MYHOST53 kernel:  connection4:0: iscsi: detected conn
error (1011)
Mar 17 23:46:18 MYHOST53 iscsid: Kernel reported iSCSI connection 4:0
error (1011) state (3)
Mar 17 23:46:20 MYHOST53 iscsid: received iferror -38
Mar 17 23:46:20 MYHOST53 last message repeated 2 times
Mar 17 23:46:20 MYHOST53 iscsid: connection4:0 is operational after
recovery (1 attempts)
Mar 18 04:04:27 MYHOST53 kernel: scsi 2:0:0:0: rejecting I/O to dead
device
Mar 18 04:04:27 MYHOST53 kernel: EXT3-fs error (device sdc1):
ext3_find_entry: reading directory #2 offset 0
Mar 18 04:04:27 MYHOST53 kernel: scsi 2:0:0:0: rejecting I/O to dead
device
Mar 18 04:04:27 MYHOST53 kernel: Buffer I/O error on device sdc1,
logical block 0
Mar 18 04:04:27 MYHOST53 kernel: lost page write due to I/O error on
sdc1
Mar 18 04:04:27 MYHOST53 kernel: scsi 2:0:0:0: rejecting I/O to dead
device
Mar 18 04:04:27 MYHOST53 kernel: EXT3-fs error (device sdc1):
ext3_find_entry: reading directory #2 offset 0
Mar 18 04:04:27 MYHOST53 kernel: scsi 2:0:0:0: rejecting I/O to dead
device
Mar 18 04:04:27 MYHOST53 kernel: Buffer I/O error on device sdc1,
logical block 0
Mar 18 04:04:27 MYHOST53 kernel: lost page write due to I/O error on
sdc1
Mar 18 14:56:49 MYHOST53 kernel: scsi 2:0:0:0: rejecting I/O to dead
device
Mar 18 14:56:49 MYHOST53 kernel: ext3_abort called.
Mar 18 14:56:49 MYHOST53 kernel: EXT3-fs error (device sdc1):
ext3_journal_start_sb: Detected aborted journal

So quite a serious error.  I'm assuming that it would not be anything
to do with the iscsi time-out parm changes we made previosuly....  the
disk was not under any i/o stress at all when the error occurred.


Thanks,
Richard.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"open-iscsi" group.
To post to this group, send email to open-iscsi@googlegroups.com
To unsubscribe from this group, send email to 
open-iscsi+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/open-iscsi
-~----------~----~----~----~------~----~------~--~---

Reply via email to