if the letter is already taken ..can you rename to something other emcpower device ..that will free up the slot for you to maneuver around. Also i see that your policy is set to BasicFailover ..are you using the licensed version?
Currently these two machines are not licensed. I'm sure my manager has requested new license for these new machines. Is there a correlation between emcpower* pseudo-devices and an unlicensed PowerPath version ?
Now I'm reading the man page of emcpadm and trying to use the rename options.
no correlation at all ..just wanted to make sure that policy is set to ClarOpt if you do have license installed , once you do get the license, install it and set policy to ClarOpt to get the benefits of load-balancing/failover.
I've read your suggested doc and it was useful just like the "man emcpadm" command.
Just for other readers. I solved using the following commands: From node1: emcpadm getused and then emcpadm rename -s emcpowera -t emcpowere emcpadm rename -s emcpowerb -t emcpowerf emcpadm rename -s emcpowerd -t emcpowerg
From node2: emcpadm getused and then emcpadm rename -s emcpowerb -t emcpowere emcpadm rename -s emcpowera -t emcpowerf emcpadm rename -s emcpowerc -t emcpowerg
So rename pseudos' does not work well on boot form san devices. How to you rename the pseudo of a boot from san device because for the device in use errors not due to the pseudo name taken but that its an open boot disk on Linux?
However, if the disk is busy, and with this being a boot from SAN, I'd expect it is, you may need to consider taking a new disk and renaming it to suit your needs, then migrating the kernel over to it.
rawstorage
3 Apprentice
•
423 Posts
0
March 26th, 2008 17:00
dynamox
9 Legend
•
20.4K Posts
0
March 26th, 2008 17:00
aco1
10 Posts
0
March 26th, 2008 17:00
Currently these two machines are not licensed. I'm sure my manager has requested new license for these new machines.
Is there a correlation between emcpower* pseudo-devices and an unlicensed PowerPath version ?
Now I'm reading the man page of emcpadm and trying to use the rename options.
dynamox
9 Legend
•
20.4K Posts
0
March 26th, 2008 17:00
aco1
10 Posts
1
March 26th, 2008 17:00
Just for other readers. I solved using the following commands:
From node1:
emcpadm getused
and then
emcpadm rename -s emcpowera -t emcpowere
emcpadm rename -s emcpowerb -t emcpowerf
emcpadm rename -s emcpowerd -t emcpowerg
From node2:
emcpadm getused
and then
emcpadm rename -s emcpowerb -t emcpowere
emcpadm rename -s emcpowera -t emcpowerf
emcpadm rename -s emcpowerc -t emcpowerg
Thanks,
Marco
wzglc6
1 Message
0
June 3rd, 2008 01:00
I know, it is not used. This happens on a linux 5.0 x64 system.
Any help is appreciated.
Stefan
rawstorage
3 Apprentice
•
423 Posts
0
June 3rd, 2008 23:00
the command "emcpadm getfreepseudos" will show you if this if free or not.
This may be something SAC should take a look at if the device is not showing up there and is not showing in powermt display dev=all.
ibmpdc2
3 Posts
0
April 5th, 2021 16:00
So rename pseudos' does not work well on boot form san devices. How to you rename the pseudo of a boot from san device because for the device in use errors not due to the pseudo name taken but that its an open boot disk on Linux?
Dell-DylanJ
4 Operator
•
2.9K Posts
0
April 6th, 2021 09:00
Hello,
You might give this article a look to see if it helps you at all:
https://dell.to/3wzTEM8
However, if the disk is busy, and with this being a boot from SAN, I'd expect it is, you may need to consider taking a new disk and renaming it to suit your needs, then migrating the kernel over to it.
Please let me know if this helps.