Sponsored Content
Top Forums UNIX for Advanced & Expert Users How to increase PV's in a Volume group ? Post 302118377 by funksen on Monday 21st of May 2007 05:12:35 PM
Old 05-21-2007
which os?

if aix 4.3+ it can be done without downtime with

extendvg <vgname> <hdiskname>
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

LVM - Extending Logical Volume within Volume Group

Hello, I have logical volume group of 50GB, in which I have 2 logical volumes, LogVol01 and LogVol02, both are of 10GB. If I extend LogVol01 further by 10GB, then it keeps the extended copy after logical volume 2. I want to know where it keeps this information Regards Himanshu (3 Replies)
Discussion started by: ghimanshu
3 Replies

2. AIX

Moving a Logical Volume from one Volume Group to Another

Does anyone have any simple methods for moving a current logical volume from one volume group to another? I do not wish to move the data from one physical volume to another. Basically, I want to "relink" the logical volume to exist in a different volume group. Any ideas? (2 Replies)
Discussion started by: krisw
2 Replies

3. AIX

Logical volume name conflict in two volume group

Hello, I am a french computer technician, and i speak English just a little. On Aix 5.3, I encounter a name conflict logical volume on two volume group. The first volume lvnode01 is OK in rootvg and mounted. It is also consistent in the ODM root # lsvg -l rootvg |grep lvnode01 ... (10 Replies)
Discussion started by: dantares
10 Replies

4. AIX

Adding a Volume Group to an HACMP Resource Group?

Hi, I have a 2 node Cluster. Which is working in active/passive mode (i.e Node#1 is running and when it goes down the Node#2 takes over) Now there's this requirement that we need a mount point say /test that should be available in active node #1 and when node #1 goes down and node#2 takes... (6 Replies)
Discussion started by: aixromeo
6 Replies

5. HP-UX

Increase Size of a Volume Group

Hi I have hp-ux 10.20 I have have my operating system VG of 7 GB in a 36Gb disk. So I have like 29GB of unused disk space. There is any way to increase my VG size, or to add another VG in the same disk so I can use all the disk space? Another question, what is the maximun size that a VG can ... (10 Replies)
Discussion started by: pmoren
10 Replies

6. UNIX for Dummies Questions & Answers

Confusion Regarding Physical Volume,Volume Group,Logical Volume,Physical partition

Hi, I am new to unix. I am working on Red Hat Linux and side by side on AIX also. After reading the concepts of Storage, I am now really confused regarding the terminologies 1)Physical Volume 2)Volume Group 3)Logical Volume 4)Physical Partition Please help me to understand these concepts. (6 Replies)
Discussion started by: kashifsd17
6 Replies

7. UNIX for Dummies Questions & Answers

How to create a volume group, logical volume group and file system?

hi, I want to create a volume group of 200 GB and then create different file systems on that. please help me out. Its becomes confusing when the PP calculating PP. I don't understand this concept. (2 Replies)
Discussion started by: kamaldev
2 Replies

8. AIX

Increase filesystem and or logical volume

Hi all, Do i need to increase the logical volume each time i increase the filesystem? or is enough to increase the filesystem and the logical volume get increase automatically? extendlv hd4 1 chfs -a size=2G /tmp or just chfs -a size=2G /tmp Code tags! (4 Replies)
Discussion started by: prpkrk
4 Replies

9. Red Hat

No space in volume group. How to create a file system using existing logical volume

Hello Guys, I want to create a file system dedicated for an application installation. But there is no space in volume group to create a new logical volume. There is enough space in other logical volume which is being mounted on /var. I know we can use that logical volume and create a virtual... (2 Replies)
Discussion started by: vamshigvk475
2 Replies

10. Shell Programming and Scripting

Increase volume in steps

I would like to modify this so the buzzer starts at 15% and goes up to 30% in volume while it is playing. amixer -D pulse sset Master 30% > /dev/null 2>&1 cvlc --play-and-exit /usr/share/sounds/My_Sounds/Alarm-sound-buzzer.mp3 > /dev/null 2>&1 echo 'TIME IS UP.' gxmessage -fg blue... (2 Replies)
Discussion started by: drew77
2 Replies
DOWNTIMED(8)						      System Manager's Manual						      DOWNTIMED(8)

NAME
downtimed - system downtime monitoring and reporting daemon SYNOPSIS
downtimed [-D] [-d datadir] [-l log] [-p pidfile] [-S] [-s sleep] downtimed -v DESCRIPTION
The downtimed daemon waits in the background, frequently updating a time stamp file on the disk. If the daemon is killed with a signal associated with a normal system shutdown procedure, it will record the shutdown time on the disk. When the daemon is restarted during the next boot process, it will report how long the system was down and whether it was properly shut down or crashed. The downtime report is output to the system log or to a specified log file. Also a record is appended to the downtime database. OPTIONS
-D Do not create nor update the downtime database. -d datadir The directory where the time stamp files as well as the downtime database are located. The default directory is determined at com- pile time. -l log Logging destination. If the argument contains a slash (/) it is interpreted to be a path name to a log file, which will be created if it does not exist already. Otherwise it is interpreted as a syslog facility name. The default logging destination is "daemon" which means that the messages are written to syslog with the daemon facility code. -p pidfile The location of the file which keeps track of the process ID of the running daemon process. The system default location is deter- mined at compile time. -S Normally fsync(2) is performed after each update of the time stamp. This option disables the fsync(2). It reduces the load on the disk system but makes the downtime measurement less reliable. This option is not available on all systems. -s sleep Defines how long to sleep between each update of the on-disk time stamp file. More frequent updates result in more accurate downtime reporting in the case of a system crash. Less frequent updates decrease the amount of disk writes performed. The default is to sleep 15 seconds between eacch update. If you are using a flash memory based SSD or other disk which has limited amount of write cycles per block, it might be a good idea to set the sleep time to a higher value to prolong the lifetime of the storage device. -v Display the program version number, copyright message and the default settings. SIGNALS
SIGHUP Close and re-open the output log. Use in case you want to rotate the log file. SIGTERM and SIGINT Terminate gracefully. These signals signify that a graceful system shutdown is in process. EXIT STATUS
The daemon exits 0 on success, and >0 if an error occurs. SEE ALSO
downtimes(1), syslog.conf(5), http://dist.epipe.com/downtimed/ BUGS
The reporting accuracy in case of a system crash depends on how often the time stamp is updated. Finding out the system startup time is very operating system specific. If the program does not have specific code to support your operat- ing system, it assumes that the system started when the daemon started. Reporting is inaccurate if the system clock changes during system downtime or startup process. Daylight saving time changes have no effect as all calculations are done using UTC. COPYRIGHT
Copyright (C) 2009-2011 EPIPE Communications. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBU- TORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCURE- MENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABIL- ITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. The views and conclusions contained in the software and documentation are those of the authors and should not be interpreted as represent- ing official policies, either expressed or implied, of EPIPE Communications. version 0.5 2011-03-02 DOWNTIMED(8)
All times are GMT -4. The time now is 03:34 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy