Skip to ContentSkip to Footer
Start of content
- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- EMC&, 4 Node MetroCluster/SRDF
Disk Enclosures
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
-
- Forums
-
Blogs
- Alliances
- Around the Storage Block
- Behind the scenes @ Labs
- HPE Careers
- HPE Storage Tech Insiders
- Infrastructure Insights
- Inspiring Progress
- Internet of Things (IoT)
- My Learning Certification
- OEM Solutions
- Servers: The Right Compute
- Shifting to Software-Defined
- Telecom IQ
- Transforming IT
- Infrastructure Solutions German
- L’Avenir de l’IT
- IT e Trasformazione Digitale
- Enterprise Topics
- ИТ для нового стиля бизнеса
- Blogs
-
Quick Links
- Community
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Contact
- Email us
- Tell us what you think
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Enterprise.nxt
- Marketplace
- Aruba Airheads Community
-
Forums
-
Blogs
-
InformationEnglish
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
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
10-11-2000 06:28 AM
10-11-2000 06:28 AM
EMC&, 4 Node MetroCluster/SRDF
Hello together,
we wan't to set up a new Cluster Package in a METROCLUSTER/SRDF.
The Volume Group in this Package should include one Disk and his alternate link from the EMC?. The Disk is mapped to each HOST Adapter from every 4 Systems. We check this and it seems to be all right?!
NODE1:
No we create the Directory for the Volume Group, create the group Devicefile (No duplicated minor Number in use).
We create the VG on this Disk, do an vgextend to get the Alternate Link in VG.
We export the VG by using the following Command: vgexport -s -m /vg12.map vg12
After that we copied the mapfile to all other hosts.
NODE2:
Create VG Directory, group file...
No we wan't to import the VG with mapfile.
vgimport -s -m /vg12.map /dev/vg12
The vgimport appears with the following error: cross-device link error .....
After that we export this vg12 from both Systems we do an pvcreate -f to this disk
create the vg new. do the same steps as before.
We still have the same Problems.
We do an dd to the Disk, create VG new ....
Same problem.
Do you have any Ideas to this Problem?
Thanks for your help
Best regards
Tobias Bahlinger
we wan't to set up a new Cluster Package in a METROCLUSTER/SRDF.
The Volume Group in this Package should include one Disk and his alternate link from the EMC?. The Disk is mapped to each HOST Adapter from every 4 Systems. We check this and it seems to be all right?!
NODE1:
No we create the Directory for the Volume Group, create the group Devicefile (No duplicated minor Number in use).
We create the VG on this Disk, do an vgextend to get the Alternate Link in VG.
We export the VG by using the following Command: vgexport -s -m /vg12.map vg12
After that we copied the mapfile to all other hosts.
NODE2:
Create VG Directory, group file...
No we wan't to import the VG with mapfile.
vgimport -s -m /vg12.map /dev/vg12
The vgimport appears with the following error: cross-device link error .....
After that we export this vg12 from both Systems we do an pvcreate -f to this disk
create the vg new. do the same steps as before.
We still have the same Problems.
We do an dd to the Disk, create VG new ....
Same problem.
Do you have any Ideas to this Problem?
Thanks for your help
Best regards
Tobias Bahlinger
Don't worry, be happy
1 REPLY
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
10-11-2000 11:04 PM
10-11-2000 11:04 PM
Re: EMC&, 4 Node MetroCluster/SRDF
Hello together,
today we use a different minor number an everything works fine.
I think that the old minor adress was used from the Kernel our something else.
(note: When you do an Listing our search for this Adress under the directory /dev and system wide you cannot see, that this adress is used from someone else.)
Old minor adress was 0x120000 we use now 0x500000.
Best regards
Tobias Bahlinger
today we use a different minor number an everything works fine.
I think that the old minor adress was used from the Kernel our something else.
(note: When you do an Listing our search for this Adress under the directory /dev and system wide you cannot see, that this adress is used from someone else.)
Old minor adress was 0x120000 we use now 0x500000.
Best regards
Tobias Bahlinger
Don't worry, be happy
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.
End of content
United States
Hewlett Packard Enterprise International
Communities
- Communities
- HPE Blogs and Forum
© Copyright 2019 Hewlett Packard Enterprise Development LP