From: Hunter, Mark (Mark.Hunter@ANHEUSER-BUSCH.COM)
Date: Tue Jan 06 2004 - 09:59:24 EST
Probably the diag process checking to make sure the unassigned disks are ok.
You might try importing them into hostA (not auto varyon) so that the system
knows the disks are assigned to a volume group.
-----Original Message-----
From: Paul. Vanchope [mailto:cuihh6@HOTMAIL.COM]
Sent: Tuesday, January 06, 2004 7:56 AM
To: aix-l@Princeton.EDU
Subject: hdisk open failure in errpt
hostA:\>errpt
F45CFAFB 0105214504 P H hdisk91 OPEN FAILURE
F45CFAFB 0105214504 P H hdisk196 OPEN FAILURE
F45CFAFB 0105214504 P H hdisk90 OPEN FAILURE
F45CFAFB 0105214504 P H hdisk195 OPEN FAILURE
F45CFAFB 0105214504 P H hdisk89 OPEN FAILURE
F45CFAFB 0105214504 P H hdisk194 OPEN FAILURE
F45CFAFB 0105214504 P H hdisk88 OPEN FAILURE
F45CFAFB 0105214504 P H hdisk193 OPEN FAILURE
F45CFAFB 0105214504 P H hdisk87 OPEN FAILURE
F45CFAFB 0105214504 P H hdisk192 OPEN FAILURE
F45CFAFB 0105214504 P H hdisk86 OPEN FAILURE
These disks are all from IBM ESS F20. hostA and hostB share these disks
(non-concurrent mode).
I created a vg called usrvg for hostB using all these disks.
And finally i "varyonvg usrvg" on hostB.
So from hostA these disks didn't belong to any vg.
hostA:\>lspv | grep None
hdisk86 none None
hdisk87 none None
hdisk88 none None
hdisk89 none None
hdisk90 none None
hdisk91 none None
hdisk192 none None
hdisk193 none None
hdisk194 none None
hdisk195 none None
hdisk196 none None
I don't understand why the "OPEN FAILURE" would appear in hostA's error
report ?
What can i do to solve the problem ?
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 22:17:27 EDT