ioscan in SAM takes 10 minutes

[PCIS]

Hello
I'have already this kind of issue.

You need to publish on your san a host lun begining by zero.

cyt0d0, if you don't have this lun, you server will make a full scan to discover your SAN.

So you can try to verify, if your lun aren't protected or invalidate.

Regards

Nicolas

[Rommel T. Misa_2]

Hello all,

I did what Duncan suggested, that is, to monitor the samlog as I am issuing SAM>Disks and File Systems. Attached is the samlog. I think it's in ioscan where it takes too long. If you have time, you might want to take a look at the attachment.

Thanks,
ROMMEL

[Rommel T. Misa_2]

To Nicolas,

Do you mean that I have to have this LUN configured first? And yes, my system is connected to an SAN.

ROMMEL

[Rommel T. Misa_2]

I have attached the output of ioscan -fnk here. When I issued the command

# ioscan -fnH 0/0/14/1/0

the output of this command takes about 7 mins.

ROMMEL

[Torsten.]

Well, looks like a large SAN.

Did you separate disks and tapes by zoning?

[PCIS]

Yes Romel, you need to have this lun.

On hitachi 9500 series and tagmastore, you need to have an hosted lun than begin by 0.

ldev 3 > hosted 0
ldev 24 > hosted 1
ldev 35 > hosted 2

etc.

If you don't have this hosted lun, the system scan the full range possible hosted device 1 to 255.

Becareful if you are on a wide san, check all you storage device, maybe you'are in this case too.

Regards
Nicolas

[PCIS]

I saw,

you have /dev/dsk/c20t0d0./dev/dsk/c18t0d0

You are not in the same case than me.

You can try to remove path by path and see if something change.

Nicolas