Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: Exportvg/importvg causes corrupt LV Control Block
Operating Systems AIX Exportvg/importvg causes corrupt LV Control Block Post 302849063 by livehho on Friday 30th of August 2013 07:00:41 PM
Old 08-30-2013
Exportvg/importvg causes corrupt LV Control Block
Hi experts,

Power7 p720
AIX 6.1

This is what happened:

Code:
$ sudo importvg -y v7000_1vg hdisk6
0516-622 synclvodm: Warning, cannot write lv control block data.
0516-622 synclvodm: Warning, cannot write lv control block data.
0516-622 synclvodm: Warning, cannot write lv control block data.
0516-622 synclvodm: Warning, cannot write lv control block data.
0516-622 synclvodm: Warning, cannot write lv control block data.
0516-622 synclvodm: Warning, cannot write lv control block data.
0516-622 synclvodm: Warning, cannot write lv control block data.
0516-622 synclvodm: Warning, cannot write lv control block data.
0516-622 synclvodm: Warning, cannot write lv control block data.
0516-622 synclvodm: Warning, cannot write lv control block data.
0516-622 synclvodm: Warning, cannot write lv control block data.
0516-622 synclvodm: Warning, cannot write lv control block data.
0516-622 synclvodm: Warning, cannot write lv control block data.
0516-622 synclvodm: Warning, cannot write lv control block data.
0516-622 synclvodm: Warning, cannot write lv control block data.
0516-622 synclvodm: Warning, cannot write lv control block data.
0516-622 synclvodm: Warning, cannot write lv control block data.
0516-622 synclvodm: Warning, cannot write lv control block data.
0516-622 synclvodm: Warning, cannot write lv control block data.
0516-622 synclvodm: Warning, cannot write lv control block data.
0516-622 synclvodm: Warning, cannot write lv control block data.
v7000_1vg

Volume Group shows 'active'

Code:
$ lsvg v7000_1vg
VOLUME GROUP:       v7000_1vg                VG IDENTIFIER:  00f7974500004c0000000137ecf731f1
VG STATE:           active                  PP SIZE:        1024 megabyte(s)
VG PERMISSION:      read/write               TOTAL PPs:      3904 (3997696 megabytes)
MAX LVs:            256                      FREE PPs:       2487 (2546688 megabytes)
LVs:                21                       USED PPs:       1417 (1451008 megabytes)
OPEN LVs:           0                        QUORUM:         2 (Enabled)
TOTAL PVs:          1                        VG DESCRIPTORS: 2
STALE PVs:          0                        STALE PPs:      0
ACTIVE PVs:         1                        AUTO ON:        yes
MAX PPs per VG:     32512                                     
MAX PPs per PV:     4064                     MAX PVs:        8
LTG size (Dynamic): 256 kilobyte(s)          AUTO SYNC:      no
HOT SPARE:          no                       BB POLICY:      non-relocatable
PV RESTRICTION:     none                     INFINITE RETRY: no

Below, the fields 'TYPE' and 'MOUNT POINT' are missing

Code:
$ lsvg -l v7000_1vg
v7000_1vg:
LV NAME             TYPE       LPs     PPs     PVs  LV STATE      MOUNT POINT
loglv02                        1       1       1    closed/syncd  N/A
fslv18                         11      11      1    closed/syncd  N/A
fslv19                         200     200     1    closed/syncd  N/A
fslv20                         100     100     1    closed/syncd  N/A
fslv21                         100     100     1    closed/syncd  N/A
fslv22                         130     130     1    closed/syncd  N/A
fslv23                         100     100     1    closed/syncd  N/A
fslv24                         100     100     1    closed/syncd  N/A
fslv25                         100     100     1    closed/syncd  N/A
fslv26                         100     100     1    closed/syncd  N/A
fslv27                         100     100     1    closed/syncd  N/A
fslv28                         100     100     1    closed/syncd  N/A
fslv29                         100     100     1    closed/syncd  N/A
fslv30                         30      30      1    closed/syncd  N/A
fslv31                         30      30      1    closed/syncd  N/A
fslv32                         30      30      1    closed/syncd  N/A
fslv33                         30      30      1    closed/syncd  N/A
fslv34                         30      30      1    closed/syncd  N/A
fslv35                         10      10      1    closed/syncd  N/A
fslv36                         10      10      1    closed/syncd  N/A
fslv37                         5       5       1    closed/syncd  N/A

I tried to mount manually

Code:
$ sudo mount /dev/fslv19 /notes/d24aml06/mail1
mount: 0506-322 Cannot determine log device to use for /dev/fslv19 (/notes/d24aml06/mail1).

Log LV is missing data

Code:
$ sudo getlvcb -AT loglv02
         
         intrapolicy =  
         copies = 1 
         interpolicy =  
         lvid =  
         lvname =  
         label =  
         machine id =  
         number lps = 1 
         relocatable =  
         strict =  
         stripe width = 0 
         stripe size in exponent = 0 
         type =  
         upperbound = 0 
         fs =  
         time created  =         time modified =

Below is the evidence that the Logical Volume Control Block is corrupted

Code:
$ sudo getlvcb -AT fslv19 
         B�
         intrapolicy = � 
         copies = 1 
         interpolicy = � 
         lvid = � 
         lvname =  
         label = ���������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������� 
         machine id = ����������������� 
         number lps = 200 
         relocatable = � 
         strict = � 
         stripe width = 0 
         stripe size in exponent = 0 
         type =  
         upperbound = -21846 
         fs = �������������������������������������������������������������������������������������������������������������������������������� 
         time created  = �����������������������������������������������������������������������������   time modified = �����������������������������������������������

Unable to rebuild the LVCB

Code:
$ sudo synclvodm v7000_1vg
0516-622 synclvodm: Warning, cannot write lv control block data.
0516-622 synclvodm: Warning, cannot write lv control block data.
0516-622 synclvodm: Warning, cannot write lv control block data.
0516-622 synclvodm: Warning, cannot write lv control block data.
0516-622 synclvodm: Warning, cannot write lv control block data.
0516-622 synclvodm: Warning, cannot write lv control block data.
0516-622 synclvodm: Warning, cannot write lv control block data.
0516-622 synclvodm: Warning, cannot write lv control block data.
0516-622 synclvodm: Warning, cannot write lv control block data.
0516-622 synclvodm: Warning, cannot write lv control block data.
0516-622 synclvodm: Warning, cannot write lv control block data.
0516-622 synclvodm: Warning, cannot write lv control block data.
0516-622 synclvodm: Warning, cannot write lv control block data.
0516-622 synclvodm: Warning, cannot write lv control block data.
0516-622 synclvodm: Warning, cannot write lv control block data.
0516-622 synclvodm: Warning, cannot write lv control block data.
0516-622 synclvodm: Warning, cannot write lv control block data.
0516-622 synclvodm: Warning, cannot write lv control block data.
0516-622 synclvodm: Warning, cannot write lv control block data.
0516-622 synclvodm: Warning, cannot write lv control block data.
0516-622 synclvodm: Warning, cannot write lv control block data.

In a nutshell, after importing the VG I cannot use the data within it.

Next step?
 

10 More Discussions You Might Find Interesting

1. Programming

Reading a process control block

Hello, I want to know what call to use to read the details of a process control block in solaris ?:) (2 Replies)
Discussion started by: hmurali
2 Replies

2. UNIX for Dummies Questions & Answers

Causing a disk to be corrupt

Hmm, how to ask this without sounding too malicious... How might one go about causing a disk corruption in OS X specifically or via the command line in UNIX in general? Doesnt matter the severity of the problem, I just want to scare the person a little, then fix the problem for them. Any... (1 Reply)
Discussion started by: Yummator
1 Replies

3. AIX

nooB questions on importvg and exportvg

I don't understand the concept behind importvg and exportvg. What are some examples of when one would use this? (1 Reply)
Discussion started by: outtacontrol
1 Replies

4. Solaris

How to corrupt a superblock?

I need to corrupt a superblock of a mounted device in a soalris m/c and check recovery from an alternate superblock. How can this be done? (2 Replies)
Discussion started by: sujathan
2 Replies

5. AIX

Unable to execute varyonvg during importvg

Hello, On Aix 5.3, during importvg, the varyonvg fails: importvg -y vgtest hdisk20 0516-013 varyonvg: The volume group cannot be varied on because there are no good copies of the descriptor area. When i use manually the command varyonvg -u -b -t vgtest to force, the vg can... (3 Replies)
Discussion started by: dantares
3 Replies

6. AIX

exportvg

Hi How to check if a vg is exported from an LPAR using exportvg? Is there a command or place where we can see the list of the vg's exported from the LPAR ? Because if i run the command to varyonvg i get the below error : root@cbspsrc02 #varyonvg old_rootvg 0516-082 varyonvg: Unable to... (7 Replies)
Discussion started by: newtoaixos
7 Replies

7. HP-UX

corrupt disk

Hallo Friends, I have application X running on hpux 11.11 and oracle 9i release 2. I recently had a hardware failure on disk /dev/dsk/c2t0d0 Below is the systemlog file : root@a7dmc:/var/adm/syslog > /opt/resmon/bin/resdata -R 155713541 -r /storage/events/enclosures/gazemon/0_1_1_0.0.0... (11 Replies)
Discussion started by: kekanap
11 Replies

8. Shell Programming and Scripting

cp to copy only non-corrupt files

I don't know if I am asking this correctly, but I have a hard drive with some bad sectors and it appears that some of the data is corrupt. I am having allot of trouble copying the data to a new drive. The issue is not in copying files, but that the new drive to which files are copied is not acting... (17 Replies)
Discussion started by: LMHmedchem
17 Replies

9. AIX

importvg question

Is there a way to find the volume group name after assigning hdisk to the machine for importing it ? importvg -y <find_the_name_from_the_unknown_disk_> hdiskX Code tags and no hijacking. You should be aware of that ;) (3 Replies)
Discussion started by: filosophizer
3 Replies

10. High Performance Computing

Postgresql Database Corrupt

I am managing a linux cluster which has been build on Platform Cluster Manager PCM 1.2.1) from IBM Platform Computing. Unfortunately somebody deteled data files of postgresql from /var/lib directory. I somehow managed to start the postmaster service again, but all the administrative commands of... (2 Replies)
Discussion started by: ahsanpmd
2 Replies
All times are GMT -4. The time now is 06:01 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy