- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Filesystem extension in cluster
Categories
Company
Local Language
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
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
Community
Resources
Forums
Blogs
- 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
тАО07-23-2010 01:29 AM
тАО07-23-2010 01:29 AM
We have the following 2 (two) nodes forming one SG cluster:-
1) eccprd1
2) eccprd2
Our requirement:
Extend LVOL /dev/vg_prd1/lvol10 by 20 GB in eccprd1 server and update in eccprd2.
Observation:
vg_prd1 has 1025 free PEs, size 32 MB each, totaling to 32 GB free space available. We will take 20 GB from there.
We have worked out the following steps in our action plan (need you experts' inputs/suggestions to zero in on them):-
eccprd1: cmhaltpkg ciPR1 # halt the CI package
eccprd1: cmhaltpkg dbPR1 # halt the DB package
eccprd1: vgchange -a e /dev/vg_prd1
eccprd1: vgchange -a y /dev/vg_prd1
eccprd1: lvextend -L 119808 /dev/vg_prd1/lvol10
eccprd1: extendfs -F vxfs /dev/vg_prd1/rlvol10
eccprd1: mount /dev/vg_prd1/lvol10 /oracle/PR1/sapdata2
eccprd1: umount /oracle/PR1/sapdata2
eccprd1: vgchange -a n /dev/vg_prd1
eccprd1: vgchange -a e /dev/vg_prd1
eccprd2: vgchange -a e /dev/vg_prd1
eccprd2: vgchange -a y /dev/vg_prd1
eccprd2: mount /dev/vg_prd1/lvol10 /oracle/PR1/sapdata2
eccprd2: umount /oracle/PR1/sapdata2
eccprd2: vgchange -a n /dev/vg_prd1
eccprd2: vgchange -a e /dev/vg_prd1
During the testing phase, we plan to check package failover in debug mode:-
eccprd1: touch /etc/cmcluster/PR1/debug
eccprd2: touch /etc/cmcluster/PR1/debug
eccprd1: cmruncl
eccprd1: reboot -q # Observe failover and VG activation in eccprd2
eccprd2: cmhaltpkg ciPR1
eccprd2: cmhaltpkg dbPR1
eccprd2: cmhaltcl
eccprd1: rm /etc/cmcluster/PR1/debug
eccprd2: rm /etc/cmcluster/PR1/debug
eccprd1: cmruncl # Start the cluster normally
Queries/Confusion
=================
1) vgchange -a e /dev/vg_prd1
>> Does the same 'vgchange -a e' command work as a toggler between activating & deactivating a VG in exclusive mode?
2) What additional safety/rollback options should we consider keeping, besides the following:-
- Keep ignite backup of both nodes
- Keep complete FS backup of both nodes
- Keep /etc/cmcluster tar backup
- Keep mapfiles of all VGs
- Keep backup of the following files from both nodes
> /etc/services
> /etc/fstab
> /etc/hosts
> /etc/exports
Anything we are missing? Pls advise.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-23-2010 01:57 AM
тАО07-23-2010 01:57 AM
Re: Filesystem extension in cluster
you missed the vgexport and import activity.
please see the procedure on below thread.
http://forums11.itrc.hp.com/service/forums/questionanswer.do?admit=109447626+1279878317499+28353475&threadId=1123317
Regards,
Asif Sharif
Asif Sharif
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-23-2010 02:29 AM
тАО07-23-2010 02:29 AM
Solutioneccprd1: cmhaltpkg ciPR1 # halt the CI package
eccprd1: cmhaltpkg dbPR1 # halt the DB package
eccprd1: vgchange -a e /dev/vg_prd1
eccprd1: lvextend -L 119808 /dev/vg_prd1/lvol10
eccprd1: extendfs -F vxfs /dev/vg_prd1/rlvol10
eccprd1: mount /dev/vg_prd1/lvol10 /oracle/PR1/sapdata2
Now check the file system shows the size you expect!
eccprd1: umount /oracle/PR1/sapdata2
eccprd1: vgchange -a n /dev/vg_prd1
Test on node 2:
eccprd2: vgchange -a e /dev/vg_prd1
eccprd2: mount /dev/vg_prd1/lvol10 /oracle/PR1/sapdata2
eccprd2: umount /oracle/PR1/sapdata2
eccprd2: vgchange -a n /dev/vg_prd1
As for your questions:
1) vgchange -a e /dev/vg_prd1
>> Does the same 'vgchange -a e' command work as a toggler between activating & deactivating a VG in exclusive mode?
No,the -a e option activates in exclusive mode, and a vgchange -a n deactivates the vg, no matter what mode is was activated in.
man vgchange
2) What additional safety/rollback options should we consider keeping, besides the following:-
- Keep ignite backup of both nodes
- Keep complete FS backup of both nodes
- Keep /etc/cmcluster tar backup
- Keep mapfiles of all VGs
- Keep backup of the following files from both nodes
> /etc/services
> /etc/fstab
> /etc/hosts
> /etc/exports
Looks fine to me
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-23-2010 03:29 AM
тАО07-23-2010 03:29 AM
Re: Filesystem extension in cluster
Thanks Asif
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-23-2010 05:31 PM
тАО07-23-2010 05:31 PM
Re: Filesystem extension in cluster
fsadm -F vxfs -b 119808M /oracle/PR1/sapdata2
if you have onlinejfs that should work. Since you are not adding or removign disks from a VG you probably do not need to do the vgexport and vgimport.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-23-2010 10:12 PM
тАО07-23-2010 10:12 PM
Re: Filesystem extension in cluster
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-24-2010 01:16 AM
тАО07-24-2010 01:16 AM
Re: Filesystem extension in cluster
Your steps looks to be clear. However you refer the below links, will be supportive.
http://translate.google.co.in/translate?hl=en&sl=zh-CN&u=http://www.cnscn.org/read.php%3Ftid-16196.html&ei=uJP8SeWBCJLItge2zf3DCg&sa=X&oi=translate&resnum=1&ct=result&prev=/search%3Fq%3Dcmcheckconf%2B%252B%2Bhp-ux%26hl%3Den%26sa%3DN%26start%3D70
http://translate.google.co.in/translate?hl=en&sl=ja&u=http://www.it-folder.com/indexd.php%3Fdocument%3Dhpux_disk_lvm%26docdir%3D2008&ei=Jbj8SYfRJpGEtwfn_7GSDA&sa=X&oi=translate&resnum=3&ct=result&prev=/search%3Fq%3Dcmcheckconf%2B%252B%2Bhp-ux%26hl%3Den%26sa%3DN%26start%3D130
Rgds..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-24-2010 11:34 PM
тАО07-24-2010 11:34 PM