Anonymous_User Absent Member.
Absent Member.
1123 views

fibre storage hangs up with high I/O load.

Under heavy load, ie: backups, my netware 6.5 server takes the fibre
channel disk offline. All I can tell is that at some point an I/O does not
complete within a given timeout.
It requires a reboot to get it back back up.

My question is, what, if any, arguments can be used with the emulex, or
scsi drivers to increase the timeout it wait's for pending I/Os

Or, any other insight as to the nature of the problem would be greatly
appreciated.

Here's what is logged to the console:

<SCSIHD>CDMCallBack error! Error=80010002.Sense=0
<SCSIHD>Queue Unfrozen. scsi=38507560.
<SCSIHD>Queue Frozen in Blocking Execute called from DoStartDevice.
scsi=3850756 0. <SCSIHD>Queue Unfrozen. scsi=38507560. <SCSIHD>Queue
Unfrozen. scsi=38507560. <SCSIHD>Queue Unfrozen. scsi=38507560.
<SCSIHD>CDMCallBack error! Error=80060003.Sense=0 <SCSIHD>CDI_Object_Update!
flag=2,status=2,activate=0,device=38507560
<SCSIHD>CDMCallBack error! Error=40000.Sense=0 <SCSIHD>CDMCallBack error!
Error=40000.Sense=0 <SCSIHD>CDMCallBack error! Error=40000.Sense=0
<SCSIHD>CDMCallBack error! Error=40000.Sense=0 <SCSIHD>CDMCallBack error!
Error=40000.Sense=0 <SCSIHD>CDMCallBack error! Error=40000.Sense=0
<SCSIHD>CDMCallBack error! Error=40000.Sense=0 <SCSIHD>CDMCallBack error!
Error=40000.Sense=0 <SCSIHD>CDMCallBack error! Error=40000.Sense=0
<SCSIHD>CDMCallBack error! Error=40000.Sense=0 <SCSIHD>CDMCallBack error!
Error=40000.Sense=0 <SCSIHD>CDMCallBack error! Error=40000.Sense=0
<SCSIHD>CDMCallBack error! Error=40000.Sense=0 <SCSIHD>CDMCallBack error!
Error=40000.Sense=0 <SCSIHD>CDMCallBack error! Error=40000.Sense=0
<SCSIHD>CDMCallBack error! Error=40000.Sense=0 <SCSIHD>CDMCallBack error!
Error=40000.Sense=0 <SCSIHD>CDMCallBack error! Error=40000.Sense=0
Deactivating pool "SANPOOL"... Dismounting Volume DATA

21 Oct 2005 11:22:13 am NSS<COMN>-3.05-xxxx: comnPool.c[2534]
Pool SANPOOL: System data I/O error 20204(zio.c[1895]).
Block 501(file block 229)(ZID 3)


21 Oct 2005 11:22:19 am NSS<ZLSS>-3.05-xxxx: zlssMSAP.c[523]
MSAP: Pool "SANPOOL" read error 20206.


NLMLIB: 10/21/05 11:22:28 - remote console connection (43.0)
opened by GStockle on 10.3.3.118
NLM ASDB : NLM ASDB : Begin purging records
NLM ASDB : (DEFAULT_1397374208,9555,1)

Labels (1)
0 Likes
6 Replies
Anonymous_User Absent Member.
Absent Member.

Re: fibre storage hangs up with high I/O load.

>My question is, what, if any, arguments can be used with the emulex, or
scsi drivers to increase the timeout it wait's for pending I/Os

There are no such parameters for the SCSIHD driver. You'd have to ask
Emulex about what settings they have available.
--
Andrew C Taubman
Novell Support Forums Volunteer SysOp
http://support.novell.com/forums
(Sorry, support is not provided via e-mail)

Opinions expressed above are not
necessarily those of Novell Inc.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: fibre storage hangs up with high I/O load.

<bruce.edge@gmail.com> wrote:

> My question is, what, if any, arguments can be used with the emulex,


Only those documented; see the readme.txt file distributed with the driver
for entries such as "node_timeout". If that file is missing, the Emulex
web site has the documentation under "Support".

What version of the driver are you using? What is the storage device
SANPOOL is mounted on?

/dps

--
Using Opera's revolutionary e-mail client: http://www.opera.com/m2/
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: fibre storage hangs up with high I/O load.

On Wed, 26 Oct 2005 18:01:45 -0700, Dave Schneider
<dave.schneider@emulex.com> wrote:

> <bruce.edge@gmail.com> wrote:
>
>> My question is, what, if any, arguments can be used with the emulex,

>
> Only those documented; see the readme.txt file distributed with the
> driver for entries such as "node_timeout". If that file is missing, the
> Emulex web site has the documentation under "Support".
>
> What version of the driver are you using? What is the storage device
> SANPOOL is mounted on?
>


And which HBA?

/dps

--
Using Opera's revolutionary e-mail client: http://www.opera.com/m2/
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: fibre storage hangs up with high I/O load.

On Wed, 26 Oct 2005 18:01:45 -0700, Dave Schneider
<dave.schneider@emulex.com> wrote:

> <bruce.edge@gmail.com> wrote:
>
>> My question is, what, if any, arguments can be used with the emulex,

>
> Only those documented; see the readme.txt file distributed with the
> driver for entries such as "node_timeout". If that file is missing, the
> Emulex web site has the documentation under "Support".
>


Sorry, "delay_tout" may be more what you are looking for.

What I am looking for is more information about your setup to understand
why this happens.

/dps

--
Using Opera's revolutionary e-mail client: http://www.opera.com/m2/
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: fibre storage hangs up with high I/O load.

<bruce.edge@gmail.com> wrote:
> <SCSIHD>CDMCallBack error! Error=80010002.Sense=0
> <SCSIHD>CDMCallBack error! Error=80060003.Sense=0


Note that there is a check condition before the timeout; do you have any
information about what the check condition is?

/dps

--
Using Opera's revolutionary e-mail client: http://www.opera.com/m2/
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: fibre storage hangs up with high I/O load.

On Wed, 26 Oct 2005 08:08:30 -0700, <bruce.edge@gmail.com> wrote:

> It requires a reboot to get it back back up.
>


"scan for new devices" doesn't bring it back?

/dps

--
Using Opera's revolutionary e-mail client: http://www.opera.com/m2/
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.