Sponsored Content
Special Forums Hardware Filesystems, Disks and Memory Expanding a volume group with system-config-lvm Post 302771371 by mmulqu on Wednesday 20th of February 2013 12:38:41 PM
Old 02-20-2013
The uninitialized space I saw was not the new space. I found that the space was available after I rebooted the server.
 

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

activating volume group on system after higher level aix installation

Hi, if I do install aix 5.3 on the rootvg of an aix 4.3.3 system (having rootvg and data1vg), is it possible to varyonvg the data1vg after the installation ? (any caution ?) (1 Reply)
Discussion started by: astjen
1 Replies

4. 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

5. 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

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. Red Hat

Removing LVM Volume Group that doesn't exist anymore

Our SAN administrator decided to unpresent then destroy LUN's we were actively using as a volume group (all PV's in said volume group). Now every time I do a pvscan or whatever it complains about I/O errors trying to access those PV's. How do I get it to forget the VG existed completely? vgreduce... (7 Replies)
Discussion started by: thmnetwork
7 Replies

8. 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

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. UNIX for Advanced & Expert Users

[REDHAT7] Adding LVM volume

Dear community, is it possible to add more volumes to actual LVM disk? I have the following: # lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 120G 0 disk ├─sda1 8:1 0 500M 0 part /boot └─sda2 ... (0 Replies)
Discussion started by: Lord Spectre
0 Replies
EXPORTFS(4)						     Kernel Interfaces Manual						       EXPORTFS(4)

NAME
exportfs, srvfs - network file server plumbing SYNOPSIS
exportfs [ -an ] [ -c ctlfile ] srvfs name dir DESCRIPTION
Exportfs is a user level file server that allows Plan 9 compute servers, rather than file servers, to export portions of a name space across networks. The service is started either by the cpu(1) command or by a network listener process. An initial protocol establishes a root directory for the exported name space. The connection to exportfs is then mounted, typically on /mnt/term. Exportfs then acts as a relay file server: operations in the imported file tree are executed on the remote server and the results returned. This gives the appear- ance of exporting a name space from a remote machine into a local file tree. The -a option instructs exportfs to authenticate the user, usually because it is being invoked from a remote machine. The -n option disallows export to user none. The -c options specifies a network control file onto which exportfs will push the fcall line discipline. This option is intended for net- works that do not preserve read/write boundaries. The cpu command uses exportfs to serve device files in the terminal. The import(4) command calls exportfs on a remote machine, permitting users to access arbitrary pieces of name space on other systems. Srvfs uses exportfs to create a mountable file system from a name space: a subsequent mount (see bind(1)) of /srv/name will reproduce the name space rooted at dir. One might use srvfs to enable mounting of an FTP file system (see ftpfs(4)) in several windows. SOURCE
/sys/src/cmd/exportfs /sys/src/cmd/srvfs.c EXPORTFS(4)
All times are GMT -4. The time now is 02:14 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy