Can not mount vxfs volume when I restart server?

[kingsan168]

Hi,

I finished to install HPVM when I restart the server. I got many error as follow.

Checking for LVM volume groups and Activating (if any exist)
Volume group "/dev/vg00" is already active on this system.
Activated volume group
Volume group "/dev/vg01" has been successfully changed.
Resynchronized volume group /dev/vg00
Checking vxfs file systems
Resynchronized volume group /dev/vg01
UX:vxfs fsck: INFO: V-3-20913: /dev/vg00/lvol3:sanity check: root file system OK (mounted read/write)
UX:vxfs fsck: INFO: V-3-20948: /dev/vg00/lvol1:/dev/vg00/lvol1 is currently moun ted
UX:vxfs fsck: ERROR: V-3-20914: /dev/vg00/lvol1:sanity check: /dev/vg00/lvol1 al ready mounted
UX:vxfs fsck: INFO: V-3-20915: /dev/vg00/lvol4:sanity check: /dev/vg00/lvol4 OK
UX:vxfs fsck: INFO: V-3-20915: /dev/vg00/lvol5:sanity check: /dev/vg00/lvol5 OK
UX:vxfs fsck: INFO: V-3-20915: /dev/vg00/lvol6:sanity check: /dev/vg00/lvol6 OK
UX:vxfs fsck: INFO: V-3-20915: /dev/vg00/lvol7:sanity check: /dev/vg00/lvol7 OK
UX:vxfs fsck: INFO: V-3-20915: /dev/vg00/lvol8:sanity check: /dev/vg00/lvol8 OK
UX:vxfs fsck: ERROR: V-3-20012: /dev/vg01/fedora:not a valid vxfs file system
UX:vxfs fsck: ERROR: V-3-20012: /dev/vg01/winsrv:not a valid vxfs file system
UX:vxfs fsck: ERROR: V-3-20012: /dev/vg01/fedora:not a valid vxfs file system
/dev/vg01/fedora:invalid super-block
UX:vxfs fsck: ERROR: V-3-20694: /dev/vg01/fedora:cannot initialize aggregate
/dev/vg01/fedora:file system check failure, aborting ...
UX:vxfs fsck: ERROR: V-3-20012: /dev/vg01/winsrv:not a valid vxfs file system
/dev/vg01/winsrv:invalid super-block
UX:vxfs fsck: ERROR: V-3-20694: /dev/vg01/winsrv:cannot initialize aggregate
/dev/vg01/winsrv:file system check failure, aborting ...
couldn't fix vxfs filesystems, manual intervention needed


After logging to the system, I mount the volume manally but not success to mount.
# mount /dev/vg01/fedora /var/fedora
/dev/vg01/fedora: unrecognized file system

If I run on HPVM. What filesystem is suitable for HPVM?

Thank you.

[Eric SAUBIGNAC]

Bonjour,

==> If I run on HPVM. What filesystem is suitable for HPVM?

On the host, any one which is suitable for HP-UX
In the geust, any one which is suitable for th OS installed in the guest


==> After logging to the system, I mount the volume manally but not success to mount.
# mount /dev/vg01/fedora /var/fedora
/dev/vg01/fedora: unrecognized file system


Well this thread has something to do with your previous one : "HPVM create error" @ http://h30499.www3.hp.com/t5/Virtualization/HPVM-create-error/m-p/4759255#M2829 . Right ?

In fact I guess that you use /dev/vg01/fedora as a virtual device for an HPVM Guest. So you can't mount it on the host itself. 2 reasons :

- It is a resource used by the virtual machine guest. You can't use it for something else. Outside a cluster, do you use on a second box a disk owned by a given box ? No. It is the same thing there.

- /dev/vg01/fedora is an LVM logical volume at host level. From the virtual machine guest point of view, it is a virtual disk used for the system. So a LVM structure has been built on it to support vg00. In fact an LVM structure (Guest's vg00) above an other LVM structure (hosts's /dev/vg01/fedora).

From host point of view, can you play whith this double LVM layer ? Very difficult to ... ! And don't try to create a file system on /dev/vg01/fedora, or you will have to install again the virtual machine ... ;-)


In fact, I now understand why in your previous thread you had some warnings around restricted devices. I guess that /dev/vg00/rfedora was mounted in the host. Right ?

Eric

[kingsan168]

You mean that the virtual guest does not mount on vg01 volume group, so change to mount on vg00 volume group to build a virtual machine? Right!

[Eric SAUBIGNAC]

... ? sorry, but I did not understood your latest post ?

What I wanted to say is that it doesn't matter which logical volume (in vg00 or vg01 or ...) of the host is used as a virtual disk for the guest, but this logical volume MUST NOT BE USED in any way BY THE HOST itself.

[Jose Mosquera]

Hi,

This last reboot due to an abrupt interruption of the system?
Any change or addition of disks or inside areas before the last reboot?
Are you on LVM or VxVM?

Rgds.

[kingsan168]

Hi, Jose,

I open a sam and check the volume type is LVM vxfs/HPVM. How can change the volume type as VxVM if i run a virtual machine?

Thank.