ioscan -fnC disk hanging on 11.31

[Mike_305]

Hello,

We have 11.31 system and iosca command hangs, any idea. As per HP's suggestion I have loaded the new ioscan patch anf that didnot help.

PHCO_41898 1.0 ioscan(1M) cumulative patch

Appreciate the help in advance.

Regards,

MJ

[g3jza]

Hi,

while running the ioscan, try logging from another console and type #ioscan -kfn or #ioscan -kfnN respectively , look for SCANNING / SCAN field under particular HW path, to see where the ioscan got stuck for longer, than it should...

Might be a problem with some component....

[Torsten.]

A hung ioscan is most of the times caused by a bad disk - I would check the syslog, try ioscan with "-k" option and check the vgdisplay status for an unavailable disk.

[g3jza]

I didn't noticed the subject of the thread that you did a disk scan,
then try just #ioscan -kfnC disk , to see on which disk it got stuck... and troubleshoot further...

[Mike_305]

Hello,

Thanks for the quick reply. But "ioscan -kfnC disk" this works no issue. The issue is when we try to scan the new disk using "ioscan -fnC disk"

Regards,

MJ

[g3jza]

Hi,
I mean, try running the regular
#ioscan -fnC disk

and then simultaneously from the other console:
#ioscan -kfnC disk

to see, where the SCANNING / SCAN takes place and takes longer, than it normally should.

[Mike_305]

Hello Again,

Still no luck, ioscan -fnC disk from one session hangs forever and from another session like you suggested running ioscan -kfnC disk finished in seconds.

Regards,

MJ

[Ismail Azad]

Hey M,

Well Torsten has given you the hint that it could be a bad disk....

> The issue is when we try to scan the new disk using "ioscan -fnC disk"

Well how about rescanning the tree without the new disk if you have inserted a new one as you mention --new disk--.

Or you can go the Bill Hassell school of thought where you use an ioscan -f -H <> and keep trying until you hit the command that hangs.

Regards
Ismail Azad

[Bill Hassell]

Most problems with ioscan delays are caused by fibre LUNs that are no longer working. This can be caused by bad mapping in a SAN switch or in the controller. Contact your SAN admin and fix the mapping and/or setup for the problem LUNs.

[g3jza]

M7877: You still didn't comprehend, what I was trying to say :) .
#ioscan -fnC disk (from one console)
#ioscan -kfnC disk (wait for a couple of seconds since the 'ioscan -fnC disk' and run this command and then in the output look for 'SCAN' word, which means that the HW path might be problematic.)