Unable to extend file system


 
Thread Tools Search this Thread
Operating Systems AIX Unable to extend file system
# 8  
Old 08-07-2017
Sorry for being late, had a few busy days.

Yes, this is a VIOS and you should be root to do changes on a filesystem.

The problem you are facing is - as rbatte1 has already stated - that one of the (physical?) disks the rootvg consists of seems to be missing.

The LVM in short: VGs can consist of one or several "PV"s (physical volumes - disks) and each PV is cut up into "PP"s (physical partitions) of the same size (usually somewhere between 2MB and 2GB). Every logical volume (LV, basically raw disk space which can be formatted into a FS but also be used as paging space or whatever) consists of one or more such PPs mapped to "LP"s (logical partitions). Mirroring, like what you are using, is done by assigning 2 PPs to every LP.

The first thing you need to do is to get rid of the missing disk. If it is possible the best way to do so is to reconnect the removed disk, then remove it from the VG (the command is "reducevg", once it is empty - which is not the case right now). Only then remove it physically again. I suppose this is not possible and the physical disk is long gone. Therefore:

You need to first determine what has been on the 8 used PPs. If you are lucky it was only the copy of the dump-device which are shown as missing in the listing you provided. Try a rmlvcopy command to do so (see the man page for details). If this works and the missing disk is empty continue to remove the missing disk from the VG.

If this doesn't work: report back. It is possible to get the LV- and VG-information back to order, but only by (quite complicated) low-level methods. If it works with the high-level methods then these are preferable, so try these first.

I hope this helps.

bakunin
# 9  
Old 08-08-2017
I found the lv that has this disk, but when I try to remove it , I get the following error

Code:
vios:/home/padmin$ lslv -l lg_dumplv
0516-304 : Unable to find device id 0002ef4df616f969 in the Device
        Configuration Database.
lg_dumplv:N/A
PVID              COPIES        IN BAND       DISTRIBUTION
0002ef4df616f969  008:000:000   100%          000:008:000:000:000
hdisk0            008:000:000   100%          000:008:000:000:000
vios:/home/padmin$

vios:/home/padmin$ rmlvcopy lg_dumplv 1 0002ef4df616f969
0516-076 lreducelv: Cannot remove last good copy of stale partition.
        Resynchronize the partitions with syncvg and try again.
0516-922 rmlvcopy: Unable to remove logical partition copies from
        logical volume lg_dumplv.
vios:/home/padmin$

vios:/home/padmin$ lslv -m lg_dumplv
0516-304 : Unable to find device id 0002ef4df616f969 in the Device
        Configuration Database.
lg_dumplv:N/A
LP    PP1  PVID1             PP2  PVID2             PP3  PVID3
0001  0116 0002ef4df616f969  0115 hdisk0
0516-304 : Unable to find device id 0002ef4df616f969 in the Device
        Configuration Database.
0002  0117 0002ef4df616f969  0116 hdisk0
0516-304 : Unable to find device id 0002ef4df616f969 in the Device
        Configuration Database.
0003  0118 0002ef4df616f969  0117 hdisk0
0516-304 : Unable to find device id 0002ef4df616f969 in the Device
        Configuration Database.
0004  0119 0002ef4df616f969  0118 hdisk0
0516-304 : Unable to find device id 0002ef4df616f969 in the Device
        Configuration Database.
0005  0120 0002ef4df616f969  0119 hdisk0
0516-304 : Unable to find device id 0002ef4df616f969 in the Device
        Configuration Database.
0006  0121 0002ef4df616f969  0120 hdisk0
0516-304 : Unable to find device id 0002ef4df616f969 in the Device
        Configuration Database.
0007  0122 0002ef4df616f969  0121 hdisk0
0516-304 : Unable to find device id 0002ef4df616f969 in the Device
        Configuration Database.
0008  0123 0002ef4df616f969  0122 hdisk0
vios:/home/padmin$

# 10  
Old 08-08-2017
Quote:
Originally Posted by dn888
I found the lv that has this disk, but when I try to remove it , I get the following error

[CODE]
vios:/home/padmin$ rmlvcopy lg_dumplv 1 0002ef4df616f969
0516-076 lreducelv: Cannot remove last good copy of stale partition.
Resynchronize the partitions with syncvg and try again.
0516-922 rmlvcopy: Unable to remove logical partition copies from
logical volume lg_dumplv.
vios:/home/padmin$
I hate to say it, but you are in deep kimchi. If you have any chance of reinstalling the VIOS - the virtual I/O server should hold no data itself anyway - this would probably be the best and cleanest recommendation.

As you get "5.3" from the oslevel command you are on a very old (and quite surely not any more supported) VIOS-version. The current versions are based on AIX 6.1. You can see the installed version either on the command line (the command is ioslevel) or from the HMC-GUI in the LPAR-listing display. This in itself is a danger and you should update ASAP, but i have a feeling you are going to tell me that this is not possible - right?

So you are bound to try your luck repairing the rootvg. The following is described in more detail at MichaelFelts page rootvg.net:

First you need the PVID and the VGID of the missing disk:

Code:
# lqueryvg -p <disk> -vPt

You need the displayed information later to delete the disk from the VG. Next remove the dump device which has allocated some PPs on the missing disk. Create a new dump device on the available disks if necessary.

Next you can remove the disk itself:

Code:
ldeletepv -v <VGID> -p <PVID>

NOTE that even if this is "best practice" this is a surgical operation and a certain risk is involved. A productive system, though - let alone a VIOS - is not the place to try anything even remotely risky! Do yourself a favour and have current backups (preferably mksysb-images on a NIM-server) ready before you begin!

If you have the hardware to do it: the less risky way to correct this is to create a mksysb-image and edit the /image.data file before creating it (see the command mkszfile) for details). Then you restore this mksysb to some other hardware, take another mksysb and restore that to the original hardware, replacing the original. The advantage to this is that you can test, change and retest as long as you want before taking a final decision.

I hope this helps.

bakunin
These 2 Users Gave Thanks to bakunin For This Post:
# 11  
Old 08-10-2017
0002ef4df616f969 is only referenced to lg_dumplv, no other lv uses it.

Aren't I able to just remove it from lg_dumplv or even destroy lg_dumplv and then remove 0002ef4df616f969?

What risk do I face if this disk 0002ef4df616f969 is removed from lg_dumplv ?

sysdumpdev -l shows that it is not using lg_dumplv
# 12  
Old 08-11-2017
Quote:
Originally Posted by dn888
Aren't I able to just remove it from lg_dumplv or even destroy lg_dumplv and then remove 0002ef4df616f969?
Yes. This is what i actually suggested:

Quote:
Originally Posted by bakunin
Next remove the dump device which has allocated some PPs on the missing disk. Create a new dump device on the available disks if necessary.
bakunin
This User Gave Thanks to bakunin For This Post:
# 13  
Old 08-16-2017
Actually, we should have asked that you run the command:
ioslevel - to get the version of VIOS you are running.

As you say, AIX 5.3 - that would indicate VIOS 1.X something, as all VIOS 2.X are built on AIX 6.1.

Anyway - if your problem is/was dealing with a missing disk - once you are the root prompt this article (which I wrote nearly 10 years ago) - might give you some additional info. http://www.rootvg.net/content/view/174/309/

FYI: as you are talking about lg_dumplv I believe this (the VIOS) is an AIX 6.1 system - from memory the lg_dumplv did not exist, by default, on AIX 5.3. And the normal command, i.e., "(un)mirrorvg", sadly, seems to forget lg_dumplv.
This User Gave Thanks to MichaelFelt For This Post:
# 14  
Old 08-21-2017
I managed to remove the disk from the VG

Code:
vios:/home/padmin$ lsvg -p rootvg
0516-304 : Unable to find device id 0002ef4df616f969 in the Device
        Configuration Database.
rootvg:
PV ID             PV STATE          TOTAL PPs   FREE PPs    FREE DISTRIBUTION
0002ef4df616f969  removed           546         538         110..101..109..109..109
hdisk0            active            546         454         109..89..38..109..109
hdisk3            active            546         469         109..104..38..109..109
vios:/home/padmin$
vios:/home/padmin$
vios:/home/padmin$ lqueryvg -p hdisk0 -vPt
Physical:       0002ef4df616f969                0   4
                0002ef4d0206744e                2   0
                0002ef4d02a2110a                1   0
VGid:           0002ef4d0000d60000000113f5ca39d1
vios:/home/padmin$
vios:/home/padmin$ lspv -l -v 0002ef4d0000d60000000113f5ca39d1 0002ef4df616f969
pvid=0002ef4df616f969:
LV NAME               LPs   PPs   DISTRIBUTION          MOUNT POINT
lg_dumplv             8     8     00..08..00..00..00    N/A
vios:/home/padmin$
vios:/home/padmin$ rmlv lg_dumplv
Warning, all data contained on logical volume lg_dumplv will be destroyed.
rmlv: Do you wish to continue? y(es) n(o)? y
rmlv: Logical volume lg_dumplv is removed.
vios:/home/padmin$
vios:/home/padmin$ lsvg -l rootvg
rootvg:
LV NAME             TYPE       LPs   PPs   PVs  LV STATE      MOUNT POINT
hd5                 boot       1     2     2    closed/syncd  N/A
hd6                 paging     4     8     2    open/syncd    N/A
paging00            paging     8     16    2    open/syncd    N/A
hd8                 jfs2log    1     2     2    open/syncd    N/A
hd4                 jfs2       2     4     2    open/syncd    /
hd2                 jfs2       13    26    2    open/syncd    /usr
hd9var              jfs2       5     10    2    open/syncd    /var
hd3                 jfs2       9     18    2    open/syncd    /tmp
hd1                 jfs2       31    62    2    open/syncd    /home
hd10opt             jfs2       2     4     2    open/syncd    /opt
fwdump              jfs2       1     2     2    open/syncd    /var/adm/ras/platform
dumplv              sysdump    7     7     1    open/syncd    N/A
vios:/home/padmin$
vios:/home/padmin$ ldeletepv -g 0002ef4d0000d60000000113f5ca39d1 -p 0002ef4df616f969
vios:/home/padmin$
vios:/home/padmin$ lqueryvg -p hdisk0 -vPt
Physical:       0002ef4d0206744e                2   0
                0002ef4d02a2110a                1   0
VGid:           0002ef4d0000d60000000113f5ca39d1
vios:/home/padmin$

Thank you all
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Linux

Unable to extend LV

Hi all. I have a Logical volume that I can't extend, with this error message: server171:root:/root# lvextend -L +1024M -v /dev/aplic_vg/siteminderwa_lv Finding volume group aplic_vg Archiving volume group "aplic_vg" metadata (seqno 75). Extending logical volume siteminderwa_lv to... (0 Replies)
Discussion started by: Gabriander
0 Replies

2. Solaris

Unable to create file system (newfs)

Hi I have the following cenario: I have requested a LUN from the NetApp to create a file system, and the netapp admin provide me with one as you can see below, but after following all the steps, I could not create a file system on the device: # format Searching for disks...done ... (11 Replies)
Discussion started by: fretagi
11 Replies

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

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

5. Solaris

How to extend an existing file system using SVM in solaris 10

Hi All I want to extend this file system to 120Gb: df -h /xyz Filesystem size used avail capacity Mounted on /dev/md/dsk/d80 98G 35G 62G 37% /xyzand the NetApp admin is going to give me an LUN with 22Gb. This file system is mounted on: metastat d80... (1 Reply)
Discussion started by: fretagi
1 Replies

6. Emergency UNIX and Linux Support

Not able to extend ZFS file system

Hi All, I have Solaris-10 configured with two non-global zones. All file-systems are mounted on global zone and data file-systems are mounted on non-global zone as lofs. I have added 4 luns of 100 GB each and still not able to extend a file-system. This is production server, so I can not... (5 Replies)
Discussion started by: solaris_1977
5 Replies

7. Solaris

Solaris file system unable to use available space

Hi, The solaris filesystem /u01 shows available space as 100GB, and used space as 6 GB. The Problem is when iam trying to install some software or copy some files in this file system /u01 Iam unable to copy or install in this file system due to lack of space. ofcourse the software... (31 Replies)
Discussion started by: iris1
31 Replies

8. HP-UX

Unable To Extend the Size of a Logical Volume File System

Background: # uname -a HP-UX deedee B.11.23 U ia64 4294967295 unlimited-user license deedee.rsn.hp.com:/ # bdf /opt Filesystem kbytes used avail %used Mounted on /dev/vg00/lvol6 6553600 6394216 158144 98% /opt /opt is almost full... (3 Replies)
Discussion started by: Rob Sandifer
3 Replies

9. UNIX for Advanced & Expert Users

Unable to clean up file system

Hi, Has anyone ever encountered the following scenario: I am working on a SUN server with solaris 10 installed and veritas managing the filesystem. One of the file systems has become full: df -kh /ossrc/dbdumps Filesystem size used avail capacity Mounted on... (6 Replies)
Discussion started by: eeidel
6 Replies

10. AIX

Can not extend a JFS file system

Hi, I am getting an error message when i try to increase the size of a filesystems under AIX 4.3.3: chfs: 0506-932 Can not extend a JFS file system with nbpi = 4096 and frag = 4096 past 134217728 (512 byte blocks). -> Characteristics Journaled File System ... (4 Replies)
Discussion started by: Can
4 Replies
Login or Register to Ask a Question