LVM Problem

[Edol_1]

Hi all,
I have a L1000 and 73GB disk.I need to increment a /home, well the folowing command are execute:
umount /home
lvextend -L 15000 /dev/dsk/lvol5 - ok
extendfs /dev/rdsk/lvol5
when i mount this file system this message is displayed:
mount /dev/vg00/lvol5 /home
vxfs mount: /dev/vg00/lvol5 no such device
but this files (devices) exist in /dev/vg00
can you help me
my system is hpux 11.0

[Torsten.]

This step is wrong:

extendfs /dev/rdsk/lvol5

should be:
extendfs /dev/vg00/rlvol5

Why not using SAM?
Also the lvextend should go to
/dev/vg00/lvol5

instead of
/dev/dsk/lvol5

even the mount command is wrong:
root@egroup-/etc : mount -F vxfs /dev/vg00/rlvol5
mount: /dev/vg00/rlvol5 was either ignored or not found in /etc/fstab

should be without "r"
mount /dev/vg00/lvol5 /home

or just
mount /home

[Edol_1]

oooops sorry im write wrong (in forun) some commands.
This is the message on syslog:
Apr 7 10:24:25 egroup LVM[1417]: lvextend -L 16000 /dev/vg00/lvol5
Apr 7 10:24:25 egroup LVM[1417]: Volume Group configuration for /dev/vg00 has b
een saved in /etc/lvmconf/vg00.conf
when i run extendfs:
root@egroup-/etc : extendfs /dev/vg00/rlvol5
vxfs fsck: file system needs checking
vxfs fsck: cannot extend aggregate
vxfs extendfs: Invocation of the fsck program terminated abnormally.
The file system is marked bad. Run full fsck manually.
(e.g. fsck -F vxfs /dev/vg00/rlvol5)

and fsck

root@egroup-/etc : fsck -F vxfs /dev/vg00/rlvol5
file system is mountable - log replay is not required

root@egroup-/etc : fsck -F vxfs /dev/vg00/rlvol5
file system is mountable - log replay is not required
root@egroup-/etc : extendfs /dev/vg00/rlvol5
vxfs fsck: file system needs checking
vxfs fsck: cannot extend aggregate
vxfs extendfs: Invocation of the fsck program terminated abnormally.
The file system is marked bad. Run full fsck manually.
(e.g. fsck -F vxfs /dev/vg00/rlvol5)

I dont know why this happened.

[Patrick Wallek]

What happens if you do:

# fsck -F vxfs -o full /dev/vg00/lvol5

[Anil C. Sedha]

Do the following

First as patrick mentioned, run the fsck command

Then

as mentioned earlier, run the extendfs command (increase by 1 Mb or so just for name sake) and then run extendfs.

Then run the mount command. However, make sure that you are running the commands using the right syntax as provided to you in earlier posts.

[Edol_1]

this is the ouyput of command:
root@egroup-/etc : fsck -F vxfs -o full /dev/vg00/lvol5
log replay in progress
fileset 1 primary inode 34 invalid sparse inode
fileset 1 primary inode 34 has invalid number of blocks (16)
pass0 - checking structural files
fileset 1 primary inode 34 (Sumino)
failed validation clear? (ynq)y
pass1 - checking inode sanity and blocks
pass2 - checking directory linkage
pass3 - checking reference counts
rebuild structural files? (ynq)y
pass0 - checking structural files
pass1 - checking inode sanity and blocks
pass2 - checking directory linkage
pass3 - checking reference counts
pass4 - checking resource maps
au 0 summary incorrect - fix? (ynq)y
au 1 summary incorrect - fix? (ynq)y
au 2 summary incorrect - fix? (ynq)y
au 3 summary incorrect - fix? (ynq)y
au 4 summary incorrect - fix? (ynq)y
au 5 summary incorrect - fix? (ynq)y
au 6 summary incorrect - fix? (ynq)y
au 7 summary incorrect - fix? (ynq)y
au 8 summary incorrect - fix? (ynq)y
au 9 summary incorrect - fix? (ynq)y
au 10 summary incorrect - fix? (ynq)y
au 11 summary incorrect - fix? (ynq)y
au 12 summary incorrect - fix? (ynq)y
au 13 summary incorrect - fix? (ynq)y
au 14 summary incorrect - fix? (ynq)y
au 15 summary incorrect - fix? (ynq)y
au 16 summary incorrect - fix? (ynq)y
au 17 summary incorrect - fix? (ynq)y
au 18 summary incorrect - fix? (ynq)y
au 19 summary incorrect - fix? (ynq)y
au 20 summary incorrect - fix? (ynq)y
au 21 summary incorrect - fix? (ynq)y
au 22 summary incorrect - fix? (ynq)y
au 23 summary incorrect - fix? (ynq)y
until....468 and
au 468 summary incorrect - fix? (ynq)y
OK to clear log? (ynq)y
after this the same message:
root@egroup-/etc : mount /home
vxfs mount: /dev/vg00/lvol5 is corrupted. needs checking
root@egroup-/etc : fsck -F vxfs /dev/vg00/rlvol5
log replay in progress
fileset 1 primary inode 34 invalid sparse inode
fileset 1 primary inode 34 has invalid number of blocks (16)
full file system check required, exiting ..

i belive the corrupted file system....

[Anil C. Sedha]

Edol,

You are not running the fsck command in "single user mode" with the "full" syntax.

You need to run the command as patrick mentioned

# fsck -F vxfs -o full /dev/vg00/lvol5

This will take care of the corruption issue. 99% chances are there is no issue here.

[Torsten.]

You can add a "-y" parameter to the command, so the yes-key will be pressed automatically.

[Edol_1]

Sorry, but don´t work

root@egroup-/etc : fsck -F vxfs -y -o full /dev/vg00/lvol5
log replay in progress
fileset 1 primary inode 34 invalid sparse inode
fileset 1 primary inode 34 has invalid number of blocks (16)
pass0 - checking structural files
fileset 1 primary inode 34 (Sumino)
failed validation clear? (ynq)y
pass1 - checking inode sanity and blocks
pass2 - checking directory linkage
pass3 - checking reference counts
rebuild structural files? (ynq)y
pass0 - checking structural files
pass1 - checking inode sanity and blocks
.....
au 466 summary incorrect - fix? (ynq)y
au 467 summary incorrect - fix? (ynq)y
au 468 summary incorrect - fix? (ynq)y
OK to clear log? (ynq)y
set state to CLEAN? (ynq)y
#
#
root@egroup-/etc : mount /home
vxfs mount: /dev/vg00/lvol5 no such device

[Torsten.]

"vxfs mount: /dev/vg00/lvol5 no such device"

please post a
vgdisplay -v vg00
and
lvdisplay -v /dev/vg00/lvol5