- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- problem of device file after vgextend in cluster
Disk Enclosures
1753759
Members
4792
Online
108799
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-30-2004 11:36 PM
тАО05-30-2004 11:36 PM
problem of device file after vgextend in cluster
hello
I have a cluster with 2 nodes rp5450 manage by MC/Service Guard.
My configuration is active/standby.
Since I don't have enough space in volume group I took one disk from another disk array.
then I did the following :
1)add the disk
2) ioscan -fnC disk .
I created lun 1 with the control panel of the disk array
the new disk path /dev/dsk/cXtYdZ
3)Created the physical volume
pvcreate -f //dev/dsk/cXtYdZ
4)extend the vg
vgextend /dev/vgXX /dev/dsk/cXtYdZ
1)umount the mount point
#umount /<>
2)extend the logical volume
#lvextend -L <> //dev/dsk/cXtYdZ
#extendfs /dev/dsk/cXtYdZ
3)mount the file system
#mount <>
Until the reboot everything worked correctly.
When I try to retarted the cluster, I got from sam (Cluster configuration , View Cluster Requirement )
The following errors
├в disk at /dev/dsk/c0t1d0 on node dbmsfin2 does not have ID or disk label├в
├в vgora is configured diferently on node dbmsfin1 than on node dbmsfin2
├в /dev/vgora on node dbmsfin2 does not appear to have a physical volume corresponding to /dev/dsk/c6t0d1 on node dbmsfin1├в
I notify that on 2 nodes ioscan does not return the same hardware path.
How can I have the same configuration in the 2 nodes?
May I perfom the same operation in 2 nodes?
In attachement see the ioscan report with the 2 nodes.
I found a disk between the hardware address with the device file
Disk 3 on dbmsfin1: disk 3 0/4/0/0.1.0 sdisk CLAIMED DEVICE HP C5447A
/dev/dsk/c5t1d0 /dev/rdsk/c5t1d0
Disk 3 on dbmsfin2 : disk 3 0/4/0/0.1.0 sdisk CLAIMED DEVICE HP C5447A
/dev/dsk/c4t1d0 /dev/rdsk/c4t1d0
And the difference continue with all disk of the diskarray.
Thank you for
I have a cluster with 2 nodes rp5450 manage by MC/Service Guard.
My configuration is active/standby.
Since I don't have enough space in volume group I took one disk from another disk array.
then I did the following :
1)add the disk
2) ioscan -fnC disk .
I created lun 1 with the control panel of the disk array
the new disk path /dev/dsk/cXtYdZ
3)Created the physical volume
pvcreate -f //dev/dsk/cXtYdZ
4)extend the vg
vgextend /dev/vgXX /dev/dsk/cXtYdZ
1)umount the mount point
#umount /<
2)extend the logical volume
#lvextend -L <
#extendfs /dev/dsk/cXtYdZ
3)mount the file system
#mount <
Until the reboot everything worked correctly.
When I try to retarted the cluster, I got from sam (Cluster configuration , View Cluster Requirement )
The following errors
├в disk at /dev/dsk/c0t1d0 on node dbmsfin2 does not have ID or disk label├в
├в vgora is configured diferently on node dbmsfin1 than on node dbmsfin2
├в /dev/vgora on node dbmsfin2 does not appear to have a physical volume corresponding to /dev/dsk/c6t0d1 on node dbmsfin1├в
I notify that on 2 nodes ioscan does not return the same hardware path.
How can I have the same configuration in the 2 nodes?
May I perfom the same operation in 2 nodes?
In attachement see the ioscan report with the 2 nodes.
I found a disk between the hardware address with the device file
Disk 3 on dbmsfin1: disk 3 0/4/0/0.1.0 sdisk CLAIMED DEVICE HP C5447A
/dev/dsk/c5t1d0 /dev/rdsk/c5t1d0
Disk 3 on dbmsfin2 : disk 3 0/4/0/0.1.0 sdisk CLAIMED DEVICE HP C5447A
/dev/dsk/c4t1d0 /dev/rdsk/c4t1d0
And the difference continue with all disk of the diskarray.
Thank you for
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-31-2004 01:59 AM
тАО05-31-2004 01:59 AM
Re: problem of device file after vgextend in cluster
To make it similar i would work it this way:
On dbmsfin1:
# vgexport -p -s -v -m mapfilename vgname
On dbmsfin2:
(ftp mapfile from 1 to 2 and note the /dev/vgxx/group file's minor no. on node 1)
# vgexport vgname
# mkdir /dev/vgname
# mknod /dev/vgname/group c 64
# vgimport -s -v -m mapfilename vgname
This will get you identical Special file structure for that VGxx.
Hope that helps.
Regards,
p.s. Be careful while using vgexport command without -p option. See man vgexport for more details.
On dbmsfin1:
# vgexport -p -s -v -m mapfilename vgname
On dbmsfin2:
(ftp mapfile from 1 to 2 and note the /dev/vgxx/group file's minor no. on node 1)
# vgexport vgname
# mkdir /dev/vgname
# mknod /dev/vgname/group c 64
# vgimport -s -v -m mapfilename vgname
This will get you identical Special file structure for that VGxx.
Hope that helps.
Regards,
p.s. Be careful while using vgexport command without -p option. See man vgexport for more details.
You need to know a lot to actually know how little you know
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-01-2004 02:49 AM
тАО06-01-2004 02:49 AM
Re: problem of device file after vgextend in cluster
Ok the error you are getting is because you have cluster aware volume group that has X number of disks on one node but a disk less on the second node .
You got to make sure that you have the same number of disks in the VG's on both the nodes .
When you added the disks/LUN , make sure that it is seen from both the nodes .
Make a note of the Hardware path and the device file of the new disk/LUN on the both the servers , it might be different .
Once you have that , follwo Bharat's procedure above , and you should be all right .
You got to make sure that you have the same number of disks in the VG's on both the nodes .
When you added the disks/LUN , make sure that it is seen from both the nodes .
Make a note of the Hardware path and the device file of the new disk/LUN on the both the servers , it might be different .
Once you have that , follwo Bharat's procedure above , and you should be all right .
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP