Sponsored Content
Operating Systems AIX Wierd thing about FSs and VGs Post 302145266 by mhenryj on Tuesday 13th of November 2007 02:51:55 PM
Old 11-13-2007
Wierd thing about FSs and VGs

Hello

It appears that on a regular basis, perhaps when weekly rebooting happens, not sure yet, my odm becomes out of sync.

When doing a smitty file system list by volume group, the FS type is displayed as ??? on several FSs. Always in the same VG.

I know how to fix this problem, thing is, why does this keep happening??

I am running AIX 5.1

Any ideas or suggestions would be appreciated

Thanks
Mike
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Wierd Message????

I am getting this message when I run my script. $ runscript.sh Not connected to any service! Here is the beginning of the script: # 1 - failure # # variable declaration FILEDATE=`date +"%Y%m%d"` Not connected to any service! Right after the FILEDATE gets loaded I get that... (6 Replies)
Discussion started by: lesstjm
6 Replies

2. Solaris

wierd sparc 5

Hi! I own a sparc 5 and i seem to have a strange problem. When its off, it starts by itself... Sounds a bit strange? Iknow. Does anyone know whats causing this?? Could it be the network card? or is it someting in ENV or some other configuration?? //dOzY (5 Replies)
Discussion started by: dozy
5 Replies

3. AIX

no VGs found

When I give lsvg command It says no VGs found When I give lspv,it gives a listing of all PVs corresponding to their respective VGs i.e. rootvg,uservg,etc. But when I give lspv hdisk0 It says rootvg not found in Configuration Manager Database. thanks Manu (3 Replies)
Discussion started by: b_manu78
3 Replies

4. AIX

mksysb restore ( vgs on SAN disks)

I have my application vendor looking at this but I want to do my own investigation. I restored from mksysb and I see my vgs that contain my internal disks. But I do not see my vgs that contain disks from the SAN. This scares me .. {{ Ha, ha!! My AIX expert boss just told me I have nothing... (0 Replies)
Discussion started by: Skyybugg
0 Replies

5. Shell Programming and Scripting

Wierd results with awk

Hey, I'm trying to use awk for some simple file manipulations but i'm getting soem wierd results. So i want to open up a file which looks like this: @relation 'autoMpg' @attribute a numeric @attribute b numeric @attribute c numeric @data -1.170815,0.257522,0.016416... (2 Replies)
Discussion started by: amatheny
2 Replies

6. SuSE

Remove disks from VGs in LVM

Hi, I have following set up on Open suse 11 vgdisplay pvdisplay lvdisplay I would like to remove these disks /dev/sdb and /dev/sdc from LVM and do not use them for anything.. Can anyone please help me with this ? (1 Reply)
Discussion started by: upengan78
1 Replies

7. Solaris

FSS and processor sets

I read somewhere which says """FSS can be assigned to processor sets, resulting in more sensitive control of priorities on a server than raw processor sets"" can any one tell me how we can assign FSS to processor set and how it works ? Thanx (2 Replies)
Discussion started by: fugitive
2 Replies

8. AIX

Unknown VGs

Hi Guys, I found on one of the server there are 2 VG's which I dont have any Idea of who created .. as below bash-3.00$ lsvg old_rootvg rootvg datavg altinst_rootvg altinst_rootvg under is meant for alternate disk installation.. But I'm not sure for which version of OS it was... (5 Replies)
Discussion started by: kkeng808
5 Replies

9. Solaris

In cluster configuration ora* VGs are not controlled by VCS

Need some one to explain "In cluster configuration ora* VGs are not controlled by VCS". Actually, I am not aware of this. Thanks, Rama (0 Replies)
Discussion started by: ramareddi16
0 Replies

10. Shell Programming and Scripting

Identify missing VGs

lsvg command returns rootvg mqB01vg heartbeatvg mqA01vg oracleAvg2 cevgA01 orastgevg ..... lsvg -o command returns rootvg mqB01vg heartbeatvg mqA01vg oracleAvg2 ...... (3 Replies)
Discussion started by: Daniel Gate
3 Replies
vgcfgrestore(1M)														  vgcfgrestore(1M)

NAME
vgcfgrestore - display or restore LVM volume group configuration from backup file or kernel memory SYNOPSIS
vg_name vg_name old_pv_path] pv_path vg_conf_path vg_conf_path old_pv_path] pv_path pv_path Remarks cannot be performed if the volume group is activated in shared mode. cannot be performed on devices attached to activated volume groups. Prior to restoring a backup configuration to a disk, detach the physi- cal volume from the volume group using the command (see pvchange(1M)), or deactivate the volume group using the command (see vgchange(1M)). will refuse to restore a configuration to a physical volume with a block size different than the block size stored in the configuration backup file for that physical volume. DESCRIPTION
The command restores the LVM configuration data from a default option) or alternate option) configuration backup file, or from kernel mem- ory option), to the physical volume named by pv_path. Or, it displays the configuration data on standard output option). The configuration stored for one physical volume, old_pv_path, can be copied to another physical volume pv_path option). Options and Arguments recognizes the following options and arguments: pv_path The raw (character) device path name of a physical volume that is currently online. If the option is omitted, pv_path must specify a physical volume whose configuration is stored in the configura- tion backup file. Get configuration information from the alternate configuration backup file vg_conf_path. This option is applicable to input arguments belonging to volume groups version 1.0. Forcibly restore the LVM configuration data even if the physical volume has alternate block(s) allocated inside the user data area. This option should be used with extreme caution. User is advised to fix the problem because potential data corruption could occur. Get configuration information from LVM data structures in kernel memory. The volume group containing pv_path must be activated in order to use this option. List the configuration information saved in the specified configuration backup file. Get configuration information from the default configuration backup file: vg_name is the path name of the volume group. base_vg_name is the base name of vg_name. For example, if vg_name is specified as base_vg_name is Restore the configuration information saved for physical volume old_pv_path to physical volume pv_path. This option is useful when a physical volume's name has changed since the configuration backup file was created or updated. old_pv_path must be the path name of a physical volume whose configuration is stored in the configuration backup file. It needs not be currently online. pv_path must be the path name of a physical volume that is currently online. Its configuration needs not be stored in the configuration backup file. Forcibly restore the LVM configuration data even if there is a physical volume mismatch between the kernel and the configuration backup file with the volume group still active. This option should not be used unless the configuration file is absolutely valid and up-to-date. Restoring invalid configuration data can result in data corruption later. If there are alternate physical volume links configured in the system, the following message will appear when total number of physical volumes in the kernel does not match with the configuration backup file due to missing alternate physical volume links: Mismatch between the backup file and the running kernel: Kernel indicates X disks for /dev/vgname; /etc/lvm- conf/vgname indicates Y disks. Cannot proceed with the restoration. Deactivate the Volume Group and try again. In this case, the user is advised to deactivate the volume group first, then use the command to restore configu- ration data when the volume group is unavailable. But if the volume group has to stay available and the user is absolutely sure the configuration file is correct, this option will restore data from the configuration file when the volume group stays available. Provide additional information when invoked together with option. o Additional values displayed for each path: o Disk size in kilobytes o Starting block number (kb) of the user data. o The PVkey (see Note that paths with the same key are links to the same device. Additional values displayed for each volume group: o max_pv o max_pe o max_lv o vg_version o vg_size (only volume groups version 2.0 or higher, see vgcreate(1M)) RETURN VALUE
exits with one of the following values: Successful completion. Failure. Errors occurred during the restore operation. EXTERNAL INFLUENCES
Environment Variables determines the language in which messages are displayed. If is not specified or is null, it defaults to "C" (see lang(5)). If any internationalization variable contains an invalid setting, all internationalization variables default to "C" (see environ(5)). EXAMPLES
Restore the LVM configuration information for the physical volume that was saved in the default file Force to restore the LVM configuration data when volume group is still active: Restore the LVM configuration information to physical volume using alternate configuration file List backup information saved in default configuration file Above command might display the following: Restore LVM configuration information stored for in default configuration file to physical volume Restore LVM configuration information to physical volume using LVM data structures in kernel memory. The volume group containing must be activated: AUTHOR
was developed by HP. SEE ALSO
pvchange(1M), vgcfgbackup(1M), vgchange(1M), intro(7), lvm(7). vgcfgrestore(1M)
All times are GMT -4. The time now is 01:57 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy