Hello,
I had to reinstall SP node from its "mksysb" image due to total crash of
system. The node is a rotating cluster node with shared disks (and of course
VGs, LVs, FSs). The reinstallation was successful - system i up and running
with the previous configuration. Unfortunatelly I connot "importvg" of one
shared VG because after reinstallation the major number used before by this
VG is now used by following devices:

/dev/bpf0
/dev/bpf1
/dev/bpf2
/dev/bpf3

I cannot import the VG with the other Major Number due to a lot of clients
have nfs mounts to the cluster. The running cluster node (which was not
crasched) has the proper Major Number. I have no clue how to change the
Major number of bpf* devices to be able use proper Major Number for the
shared VG.

After a lot of tests (on test environment) I found that /dev/bpf* files are
created everytime "tcpdump" is run (when I remove them, files are created
everytime after reboot). When I moved "tcpdump" binary to different location
and reboot the machine files were not created (the Major Number was not
used) but I still cannot import the VG with this Major Number.

I found the device (bpf) in CuDvDr and exactly it had the Major Number I
need for the VGs. After changing the major number of "bpf" device in ODM
(with odmchange command) I still cannot import VG with ("released???") Major
Number.

Where should I look for the Major Number yet in ODM?

If anybody met the same problem (or know a solution) please let me know.

thank you very,very much in advance,
Steven

Here is an example of how to create major numbers for a device.....

This is for /dev/hd9var, but works for all devices...you need to create
a charachter and block devices.

Vgs have a minor number of "0" BTW

do this -->

rm /dev/rhd9var
rm /dev/hd9var
mknod /dev/rhd9var c 10 6
mknod /dev/hd9var b 10 6

--
Posted via http://dbforums.com

Hi Steven,
I don't know ODM well so use this on your own risk. Better make a backup of
whole ODM before experimenting.


> with the previous configuration. Unfortunatelly I connot "importvg" of one
> shared VG because after reinstallation the major number used before by this
> VG is now used by following devices:
>
> /dev/bpf0
> /dev/bpf1
> /dev/bpf2
> /dev/bpf3

Let's say these devices have major numer = 45 and this is the same major
number you want to use for your LVM.

So:
1) rm /dev/bpf*
2a) (CuDvDr - customized Device Driver)
odmget -q"value1='bpf' and resource='ddins'" CuDvDr
CuDvDr:
resource = "ddins"
value1 = "bpf"
value2 = "45"
value3 = ""
2b)
odmget -q"value1='bpf' and resource='ddins'" CuDvDr > /tmp/one

3a)
odmget -q"value3='bpf'and resource='devno'" CuDvDr
CuDvDr:
resource = "devno"
value1 = "45"
value2 = "0"
value3 = "bpf"

CuDvDr:
resource = "devno"
value1 = "45"
value2 = "1"
value3 = "bpf"

CuDvDr:
resource = "devno"
value1 = "45"
value2 = "2"
value3 = "bpf"

CuDvDr:
resource = "devno"
value1 = "45"
value2 = "3"
value3 = "bpf"

3b) odmget -q"value3='bpf'and resource='devno'" CuDvDr > /tmp/three
4) Change all occurences of '45' in file /tmp/one and /tmp/three and
change it to some free major number. For me it was 46.
After that
odmchange -o CuDvDr -q"value1='bpf' and resource='ddins'" /tmp/one
odmchange -o CuDvDr -q"value3='bpf' and resource='devno'" /tmp/trojka
5) Run tcpdump. New devicces for bpf should be created:
# ls -l /dev |grep bpf
cr-------- 1 root system 46, 0 Jul 18 14:37 bpf0
cr-------- 1 root system 46, 1 Jul 18 14:37 bpf1
cr-------- 1 root system 46, 2 Jul 18 14:37 bpf2
cr-------- 1 root system 46, 3 Jul 18 14:37 bpf3


6) importvg -V 45 -y appvg hdisk1 (works now)

That's all. But as I said before be carefull with ODM as my suggestions
could be incorrect.

Good luck.