Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Unable to deactivate a Volume Group Post 302569431 by vbe on Monday 31st of October 2011 09:07:35 AM
Old 10-31-2011
My issue was on HP-UX...
I think it was a mismatch between what was in the different config files that were not updated at the time( unount an unused FS and mounted again elsewhere for development...) and after a reboot...
So I would start by checking with vgdisplay -v and (double)check all the LVs I see and compare with what is in fstab and mnttab
 

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. UNIX for Dummies Questions & Answers

Unable to reduce the size of volume group?

My volume group of size 200 gb. out of which only 100 gb is used by 2 logical volumes /dev/vg00/lvol0 and /dev/vg00/lvol0 respectively (both are 50 gb each). Whenever i use vgreduce command to reduce the size of volume group i get below error. # vgreduce vg00 -a Physical volume... (16 Replies)
Discussion started by: pinga123
16 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

Unable to extend volume group(VG)

Would some help me on this below I am trying to extend file system on AIX and however unable to extend the file system. 0516-306 extendvg: Unable to find physical volume 20 in the Device Configuration Database. 0516-321 extendvg: Physical volume u01-lv is not configured. 0516-792... (15 Replies)
Discussion started by: murali969
15 Replies

9. AIX

/usr/sbin/extendvg: Unable to extend volume group

Dear Expret, Help me about my issue, I trying add new disk to volume Group but error: step add new disk to volume group. 1. ~Change a Volume Group Add a Physical Volume to a Volume Group Remove a Physical Volume from a Volume Group Reorganize a Volume Group... (6 Replies)
Discussion started by: williamen
6 Replies

10. 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
mnttab(4)                                                          File Formats                                                          mnttab(4)

NAME
mnttab - mounted file system table DESCRIPTION
The file /etc/mnttab is really a file system that provides read-only access to the table of mounted file systems for the current host. /etc/mnttab is read by programs using the routines described in getmntent(3C). Mounting a file system adds an entry to this table. Unmount- ing removes an entry from this table. Remounting a file system causes the information in the mounted file system table to be updated to reflect any changes caused by the remount. The list is maintained by the kernel in order of mount time. That is, the first mounted file system is first in the list and the most recently mounted file system is last. When mounted on a mount point the file system appears as a regular file containing the current mnttab information. Each entry is a line of fields separated by <TAB>s in the form: special mount_point fstype options time where: special The name of the resource that has been mounted. mount_point The pathname of the directory on which the filesystem is mounted. fstype The file system type of the mounted file system. options The mount options. See respective mount file system man page in the SEE ALSO section below. time The time at which the file system was mounted. Examples of entries for the special field include the pathname of a block-special device, the name of a remote file system in the form of host:pathname, or the name of a swap file, for example, a file made with mkfile(1M). IOCTLS
The following ioctl(2) calls are supported: MNTIOC_NMNTS Returns the count of mounted resources in the current snapshot in the uint32_t pointed to by arg. MNTIOC_GETDEVLIST Returns an array of uint32_t's that is twice as long as the length returned by MNTIOC_NMNTS. Each pair of numbers is the major and minor device number for the file system at the corresponding line in the current /etc/mnttab snapshot. arg points to the memory buffer to receive the device number information. MNTIOC_SETTAG Sets a tag word into the options list for a mounted file system. A tag is a notation that will appear in the options string of a mounted file system but it is not recognized or interpreted by the file system code. arg points to a filled in mnttagdesc structure, as shown in the following example: uint_t mtd_major; /* major number for mounted fs */ uint_t mtd_minor; /* minor number for mounted fs */ char *mtd_mntpt; /* mount point of file system */ char *mtd_tag; /* tag to set/clear */ If the tag already exists then it is marked as set but not re-added. Tags can be at most MAX_MNTOPT_TAG long. Use of this ioctl is restricted to processes with the {PRIV_SYS_MOUNT} privilege. MNTIOC_CLRTAG Marks a tag in the options list for a mounted file system as not set. arg points to the same structure as MNTIOC_SETTAG, which identi- fies the file system and tag to be cleared. Use of this ioctl is restricted to processes with the {PRIV_SYS_MOUNT} privilege. ERRORS
EFAULT The arg pointer in an MNTIOC_ ioctl call pointed to an inaccessible memory location or a character pointer in a mnttagdesc structure pointed to an inaccessible memory location. EINVAL The tag specified in a MNTIOC_SETTAG call already exists as a file system option, or the tag specified in a MNTIOC_CLRTAG call does not exist. ENAMETOOLONG The tag specified in a MNTIOC_SETTAG call is too long or the tag would make the total length of the option string for the mounted file system too long. EPERM The calling process does not have {PRIV_SYS_MOUNT} privilege and either a MNTIOC_SETTAG or MNTIOC_CLRTAG call was made. FILES
/etc/mnttab Usual mount point for mnttab file system /usr/include/sys/mntio.h Header file that contains IOCTL definitions SEE ALSO
mkfile(1M), mount_cachefs(1M), mount_hsfs(1M), mount_nfs(1M), mount_pcfs(1M), mount_ufs(1M), mount(1M), ioctl(2), read(2), poll(2), stat(2), getmntent(3C) WARNINGS
The mnttab file system provides the previously undocumented dev=xxx option in the option string for each mounted file system. This is pro- vided for legacy applications that might have been using the dev=information option. Using dev=option in applications is strongly discouraged. The device number string represents a 32-bit quantity and might not contain cor- rect information in 64-bit environments. Applications requiring device number information for mounted file systems should use the getextmntent(3C) interface, which functions prop- erly in either 32- or 64-bit environments. NOTES
The snapshot of the mnttab information is taken any time a read(2) is performed at offset 0 (the beginning) of the mnttab file. The file modification time returned by stat(2) for the mnttab file is the time of the last change to mounted file system information. A poll(2) sys- tem call requesting a POLLRDBAND event can be used to block and wait for the system's mounted file system information to be different from the most recent snapshot since the mnttab file was opened. SunOS 5.10 20 Dec 2003 mnttab(4)
All times are GMT -4. The time now is 09:15 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy