Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

SAN disk errors LABEL: SC_DISK_ERR4

934 views
Skip to first unread message

karc...@hotmail.com

unread,
Apr 13, 2006, 11:07:29 AM4/13/06
to
I usually see following messages on our AIX nodes attached to SAN
DCB47997 0506172404 T H hdisk13 DISK OPERATION ERROR
I often hear ignoring these errors ( may be because they are temp
errors) and most of the time they appear...

And in our environment even creating deleting LVs in HACMP shared SAN
vpaths
I see some time hard and perm errors too.. like
72206E77 01/10 21:41 P H vpath99 REQUESTED OPERATION CANNOT
BE PERFORMED

Now what I do : I normally ignore temp errors, for perm errors I run
datapath query device and look for errors or close. If I don't see ( I
never saw one till date). I will ignore errpts. Most of the time I get
aware that some one was working on the the disks etc. So not alarmed.

Now please suggest some ways to handle, or being cautious, or recommend
a way to diagnose further if needed... ( Please don't mind my extra
concern here, but I love and respect your comments).

Thanks a ton........

Phil Langerholc

unread,
Apr 13, 2006, 11:16:41 AM4/13/06
to
You might want to check and see if you have a reserve conflict. You can
do an lquerypr -vh /dev/vpath and see if there is a persistent reserve
set. Are there any other errors in errpt? If you are using a switch,
you might want to check the error log on the switch. I would also check
the shark to see if any of the drives have "spared out." If you have
the call home feature though, you would get a visit from your IBM CE to
replace a bad disk.
You may also want to make sure another system does not have this disk
assigned to it that is not a part of the HA cluster. I ran into this
one time where I had 2 separate systems trying to access the same disk
and I had this issue. You might want to run a lsvpcfg and grep the
serial number against all your systems.

karc...@hotmail.com

unread,
Apr 18, 2006, 9:59:06 AM4/18/06
to
Thanks Phil,
I am still trying to understand ...and working on this...
One of the errors ( requsted operation can not be performed) may be due
to result of varyonvg -b -u and importvg -L commands, I suppose .. But
operational errors.. as I don't have access to SAN etc and I have less
knpwledge too on that... I will learn later...
Thanks gain..

0 new messages