problem increasing /stand

[Jairo Campana]

hello , I increase /stand,but when I did reboot
execute :
bdf

whdux1 # bdf
Filesystem kbytes used avail %used Mounted on
/dev/root 143360 106603 35237 75% /
/dev/vg00/lvol1 187413 67258 101413 40% /stand


before / it was in /dev/lvol3

that I made bad?


/

[Michael Tully · Accepted solution]

This can happen if you have attempted to do some LVM maintenance. The only way to properly increase /stand / or primary swap is with an ignite tape. (I hope you one) These three logical volumes are strict and contiguous, meaning the pe's (physical extents) must not be broken into pieces.

To fix your problem with /dev/root:

# lvlnboot -v (to see that everything is normal)
# mv /etc/mnttab /etc/mnttab.old
# mount -a
# vgscan

Does the size of /stand reflect what is in the logical volume size?

[sinhass]

Hi,

U can just move /etc/lvmtab file to other name and run vgscan.

-sinhass

[sinhass]

Hi,

Sorry I am wrong Pls follow what Michael Tully wrote.
-sinhass

[A. Clay Stephenson]

Your problem is more fundamental. /stand, as well as / and primary swap must ne contigiously allocated LVOL's. The only supported way to increase /stand is to do a make_tape_recovery and Ignite a new system.

[KapilRaj]

I hope u have adjusted the SWAP and increased /stand. Anyway this happens 'cause "bdf" command reads everything from /etc/mnttab and if u rename / delete this file u will see root mounted properly

rm /etc/mnttab;mount -a;bdf

Kaps

[Dave Wherry]

I'm curious as to why the volume group level of the device file was not present before you tried to increase /stand.
Your bdf shows / as using /dev/root
/stand now shows /dev/vg00/lvol1 which is correct.
You said /stand used to be /dev/lvol3
From my base install /stand is /dev/vg00/lvol1. So it looks to me like /stand is now correct but, I do not understand why / is not /dev/vg00/lvol3.
Granted you named the lvol root, and it is just a name. I do not understand why vg00 is not in the path.
They all should be /dev/vg00/lvol....

If you have a make_recovery tape I would rebuild from that and try to correct things. If not, I would try to create a make_recovery tape and then rebuild.

Of course, I have to ask the usual question. Why do you want to increase /stand? The question has been asked numerous times in the Forums and the general consensus has always been / and /stand should not be increased.

[Dave Wherry]

Sorry, one other thing. You do not have to adjust SWAP to increase /stand or any other file system.

[Pete Randall]

Dave,

The root file system (/), swap, and /stand have to be contiguous and actually the order is /stand, then swap, then /. In order to increase the size of /stand without doing an Ignite backup/restore, the only way to keep it contiguous would be to reduce swap, thus freeing up some room at the beginning of lvol2 that could be used for lvol1.

That is what the reducing swap comment was about.


Pete