Re: non-concurrent VG can be varyon on two nodes
- From: "caseyjbrotherton@xxxxxxxxx" <caseyjbrotherton@xxxxxxxxx>
- Date: Mon, 26 Nov 2007 10:59:31 -0800 (PST)
I don't understand the "as shared VG seperately using cluster LVM"
Do you mean that you used the C-SPOC utilities to create the VG?
There isn't much information in the post, but here is what comes
immediately to mind:
1) The hdisk2 and hdisk3 disks are not really the same between
the nodes. Check the pvid to make sure that they are.
If you used C-SPOC, then this shouldn't be a problem.
2) There is an option set on your storage for no-reserve policy.
This is possible on several different disk types, including IBM and
OEM disk vendors.
Use lsattr -El <diskname>
Hope this helps to give you a start.
Good luck resolving your problem
-Casey
.
- Follow-Ups:
- Re: non-concurrent VG can be varyon on two nodes
- From: Cavatina
- Re: non-concurrent VG can be varyon on two nodes
- References:
- non-concurrent VG can be varyon on two nodes
- From: Cavatina
- non-concurrent VG can be varyon on two nodes
- Prev by Date: Re: exporting DISPLAY question/problem
- Next by Date: Re: /etc/security/passwd flags corruption ?
- Previous by thread: non-concurrent VG can be varyon on two nodes
- Next by thread: Re: non-concurrent VG can be varyon on two nodes
- Index(es):