ITEM: D4674L

df shows filesystems missing, lsfs shows -- for fs size

Question:

        I have an RS/6000 which was recently struck by lightning.  I
have had the hdisk which was damaged replaced.  Now, I am trying to
reinstall AIX.  We did a weekly mksysb and then a tar backup each
night of modified files.  We have booted from diskette and reinstalled
from the mksysb.  We now are about to start bringing in nightly tar
backups but have some peculiar things we are concerned with:

1) Some filesystems are missing entirely after the restore from mksysb

2)  Can we bring our system up in normal mode and then restore from
    the tar tapes or would it be to our advantage to bring everything 
    back in single user mode?

3)  When I do a df, I notice some filesystems are not listed.  When I
    do an lsfs, the filesystems show up but the size is  --.  These are 
    not NFS mounted filesystems, which is the only time I've ever seen 
    sizes --.

We are going to do this restore tonight and would like some assistance
in recovering our data.

Response:

1) The filesystems that were missing from the mksysb tape were the
user created filesystems.  mksysb will backup the data in those
filesystems IF they are mounted at the time of the backup and they are
a part of the rootvg volume group.

2) You can restore the tar backup in normal mode.  It does not make a
difference.  It would be a good idea not to have any users logged on
while you are still in the restore process though.

3) You resolved this problem by removing and readding the filesystem.

You also encountered a problem with /usr filling up during the tar
backup. You have a WordPerfect application files that are in /usr.
You will create a new mount point /usr/wp for these files and restore
them there in order to free up space in /usr.  You will then attempt
to restore /usr again and increase /usr if necessary.

NEXT ACTION: Callback for status tomorrow morning.

Response:

Cannot increase filesystem size.  You are getting the errors 0516-010
and 0516-013.  You want to know how to increase the filesystem size?

NEXT ACTION:  Further research and callback.

Response:

The customer had already booted the system.  Reinstalled from a
"mksysb" image and reloaded all user data and applications from a tar
image.  This left hdisk1 defined (with the same SCSI id as hdisk2) in
the ODM.  Also, it did not correctly add hdisk2 to the ODM.

1) First we had to remove the hdisk1 that was no longer there.

2) After trying several different commands to attempt to define hdisk2
to the rootvg we did used the following script to fix the rootvg.

3) I dialed into his system with "cu" and "~put fixrootvg" on it so
the customer could then run it.

===============================================================================

\#!/bin/ksh \# fixrootvg - delete and rebuild rootvg info in the ODM
Database \# USAGE: fixodm PVname set -x lquerypv -p `getlvodm -p $1` -g
`getlvodm -v rootvg` >/dev/null 2>&1 if test "$?" -ne 0
  then echo "PV $1 does not appear to be in the rootvg"
  echo "Are you sure you want to continue? (y/n)"; read a
    if [ "$a" != "y" ]
      then exit 1
    fi fi

lqueryvg -p $1 -L | cut -c22-80 | cut -d" " -f1 | while read LVname do
  echo "Deleting Logical Volume: $LVname"
  rm -f /\# Devices
  odmdelete -q "parent = rootvg" -o CuDv
  odmdelete -q "name = rootvg" -o CuDv \# Dependencies
  odmdelete -q "name=rootvg" -o CuDep
  odmdelete -q "dependency = rootvg" -o CuDep \# Device Drivers
  odmdelete -q "value1 = rootvg" -o CuDvDr
  odmdelete -q "value3 = rootvg" -o CuDvDr

 rm -f /dev/rootvg

redefinevg -d $1 rootvg      \# define rootvg on hdiskX varyonvg -m1
rootvg          \# import ODM data from disk

===============================================================================

We then verified that all the commands worked.  There were a couple of
error messages;

lvgenminor         gen minor function failed updatelv:          unable
to update lv00 synclvodm:         unable to update lv00

4) We did an "lsvg -l rootvg" and all filesystems showed up.  "lv00"
also showed
   up correctly as "open/syncd".  Running an "fsck /csldata" (lv00)
failed
   saying that "filesystem /csldata" could not be found.

5) When we did a "cd /csldata" and then an "ls" it took a few seconds
but the
   command was successful.

6) A "df" and "mount" both showed everything to be correct now.



Support Line: df shows filesystems missing, lsfs shows -- for fs size ITEM: D4674L

Dated: September 1993 Category: N/A

This HTML file was generated 99/06/24~13:30:57

Comments or suggestions?
Contact us