Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

cannot get rid of a out-of-sync filesystem

Status
Not open for further replies.

stressedman

IS-IT--Management
Nov 19, 2008
3
IT
Hi all !

I cannot manage to get rid of a filesystem ot-of-sync.
Issuing the lsfs command I get:
/dev/alt_hd4 -- ## jfs -- -- yes no
but
synclvodm -v rootvg does not seem to do anything at all.
( lsvg returns rootvg).

As I need to clone copy my HDD, smit complains that can already find a filesystem with the same name:

+-----------------------------------------------------------------------------+ ATTENTION: calling new module /usr/sbin/alt_disk_copy. Please see the alt_disk_copy man page
and documentation for more details.
Executing command: {/usr/sbin/alt_disk_copy -P "all" -B -d "hdisk4"}
+-----------------------------------------------------------------------------+ Calling mkszfile to create new /image.data file.
Checking disk sizes.
Creating cloned rootvg volume group and associated logical volumes.
Creating logical volume alt_hd5
Creating logical volume alt_hd6
Creating logical volume alt_hd8
Creating logical volume alt_hd4
Creating logical volume alt_hd2
Creating logical volume alt_hd9var
Creating logical volume alt_hd3
Creating logical volume alt_hd1
Creating logical volume alt_hd10opt
Creating logical volume alt_lv00
Creating logical volume alt_loglv00
Creating logical volume alt_fslv00
Creating logical volume alt_fslv01
Creating logical volume alt_fslv02
Creating logical volume alt_fslv03
Creating logical volume alt_fslv04
Creating /alt_inst/ file system.
0505-104 alt_disk_install: crfs failed to create file system
/alt_inst/.
crfs: logical volume /dev/alt_hd4 already being used for filesystem ##.
Cleaning up.


What can I do ???
Please help
Thank you !

StressedMan
 
Hi!

Did you try to remove the lv using rmlv command?

If not succeeded, some more ideas:

You can try to eliminate the related entries manually. You should search the files /etc for such records. /etc/filesystems for example.

When there are no more file entries, you can start fiddling with ODM. Search CuAt and CuDv classes for alt_hd4. The command to do this is odmget and odmdelete/odmadd is for modify contents. Be careful, it is easy to do a big harm to the system by these commands.

Also, can you give me some command outpust, like
lsvg -p rootvg
lslv
lsfs

just to see if some impairnesses appear there. You can certainly clear sensitive data from the outouts, if you do not want to give them away.

--Trifo
 
Hi !
Thank you for the answer.

Here is the resuts of the commands you said:

lsvg -p rootvg
rootvg:
PV_NAME PV STATE TOTAL PPs FREE PPs FREE DISTRIBUTION
hdisk0 active 546 55 32..00..00..00..23

lsfs
Name Nodename Mount Pt VFS Size Options Auto Accounting
/dev/hd4 -- / jfs 262144 -- yes no
/dev/hd1 -- /home jfs 2097152 -- yes no
/dev/hd2 -- /usr jfs 4980736 -- yes no
/dev/hd9var -- /var jfs 524288 -- yes no
/dev/hd3 -- /tmp jfs 3932160 -- yes no
/proc -- /proc procfs -- -- yes no
/dev/hd10opt -- /opt jfs 524288 -- yes no

for what odmxxx commands are concerned, I'm a bit scared as this is a unique (!) production machine.
Anyway, the result of:
find . -type f -exec grep "alt_hd4" {} \; -print (issued under /etc)
is :
þR
./objrepos/CuAt

./objrepos/CuDep

./objrepos/CuDvDr

What shall I do with that ?

Thank you
Best regards

Stressedman
 
Be calm, the ODM is something like Windows registry. If you take care, you can do a lot without problems. So take care.

Also make a backup of the machine before the ODM modifying operations, or at least backup that 3 ODM class files to somewhere. If things go terribly wrong, you can restore them from a maintenance shell with rootvg access, as a last resort. So do not worry, be calm and take care.

Now, before any modifications, let's see what's in those ODM class files. To do this, issue these commands:

odmget CuAt | grep -p alt_hd4
odmget CuDep | grep -p alt_hd4
odmget CuDvDr | grep -p alt_hd4

This should show some stanzas of the mentioned ODM classes and we can see what information is stucked there.

Oops, almost forget: did you try the obvious "rmlv alt_hdisk4" command? Even the lv can be seen on lslv output?

--Trifo
 
Next time use alt_disk_inst -X to cleanup after alt_disk_copy



Tony ... aka chgwhat

When in doubt,,, Power out...
 
Hiya !

Dunno what happened but I got rid of a wrong entry in filesystems, rebooted and when I went to check what Trifo said (odmget) all of the commands returned a null string.
So I thought....and what if.....so I started the alt_disk_inst and IT WORKS !!!

Thank you ever so much for your valuable support !!!

StressedMan
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top