- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Re: vgscan at system boot
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
тАО09-28-2005 01:07 AM
тАО09-28-2005 01:07 AM
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-28-2005 01:31 AM
тАО09-28-2005 01:31 AM
Re: vgscan at system boot
This may be the same on Linux.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-28-2005 01:37 AM
тАО09-28-2005 01:37 AM
Re: vgscan at system boot
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-29-2005 12:19 AM
тАО09-29-2005 12:19 AM
Re: vgscan at system boot
I also have asked someone in the lab but it may take a day (or so) to get an answer back here.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-29-2005 12:59 AM
тАО09-29-2005 12:59 AM
Re: vgscan at system boot
did you comment both LVM initialization sections in /etc/rc.d/rc.sysinit file ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-29-2005 01:47 AM
тАО09-29-2005 01:47 AM
Re: vgscan at system boot
I have done the change on the two places.
I am now running an up2tape, perhaps it will help.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-19-2005 02:01 AM
тАО10-19-2005 02:01 AM
Re: vgscan at system boot
> So the customer has 2 choices:
> - change the "vgchange -ay" command to "vgchange -ay Volume00" in
> initrd-2.4.21-37.ELsmp.img/linuxrc every time a new initrd is created
> - reinstall the system without using LVM for the root filesystem
>
> The script /sbin/mkinitrd, which creates the linuxrc file, could be changed
> to have the required result:
>
> - make a copy of /sbin/mkinitrd
> # mv /sbin/mkinitrd /sbin/mkinitrd.orig
> # cp /sbin/mkinitrd.orig /sbin/mkinitrd
>
> - edit the script /sbin/mkinitrd
> # vi /sbin/mkinitrd
> Change the line:
> echo "vgchange -ay" >> $RCFILE
> To:
> echo "vgchange -ay Volume00" >> $RCFILE
>
> - create a new initrd file with the mkinitrd command or the
> /opt/hp/src/hp_qla2x00src/set_parm command.
>
> - reboot the system
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-19-2005 02:05 AM
тАО10-19-2005 02:05 AM
Re: vgscan at system boot
I have also made a workaround, that runs
"vgchange -a n my_vg" in rc3.d before the cluster starts.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-20-2005 12:09 AM
тАО10-20-2005 12:09 AM
SolutionOn Linux LVM, the vgchange command will write the new status to disk(s) of the volume group in question.
If your cluster is down, you can get away with your workaround.
But consider a situation when the cluster is active and node A fails. The node B takes over the disks and starts running the application.
You shutdown the node A and do some hardware maintenance. After that, you start it up again.
Now, the disks and the application are active on the node B, so node A *MUST NOT TOUCH* the disks *AT ALL* until node B stops using them.
If you use your workaround, node A will make a mark to the LVM data area of the disk, stating that the volume group is not active... without the knowledge that node B is actually using the disks and the volume group at the time!
With luck, your node B might not notice this immediately... but when it is time to do a LVM operation on node B (say, deactivate the volume group when preparing to move the package back to node A) it will get very confused.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-20-2005 05:59 PM
тАО10-20-2005 05:59 PM
Re: vgscan at system boot
Did you try this?
One of our engineers did on RedHat 4 (LVM2) and did not see that the deactivate on one node had any affect on the activated volume on the other. We've never seen any problems on RedHat 3. Also, you can deactivate a volume multiple times with no affect.
If you did try this, maybe there is something that we've missed and we may appreceate more details.
Thanks