Operating System - HP-UX
1833144 Members
3471 Online
110051 Solutions
New Discussion

Can't create a filesystem in vg that is part of the cluster configuration

 
Duda_1
Frequent Advisor

Can't create a filesystem in vg that is part of the cluster configuration

I created a lvol in a vg that is part of a serviceguard cluster (lvcreate -L 1000 /dev/vg50) then I ran "sam" to create the filesystem but I couldn't create it. The message: "No unused logical volumes were found on the system".
I deleted the lvol and recreated it but the same message appears.
HOw should I do to create the filesystem? It's normal that I can't create the filesystem from SAM?

As always thanks a million for the effort in responding

Duda!
3 REPLIES 3
Prashant Zanwar_4
Respected Contributor

Re: Can't create a filesystem in vg that is part of the cluster configuration

newfs -F vxfs /dev/vgname/lvolname

Thanks
Prashant
"Intellect distinguishes between the possible and the impossible; reason distinguishes between the sensible and the senseless. Even the possible can be senseless."
A. Clay Stephenson
Acclaimed Contributor

Re: Can't create a filesystem in vg that is part of the cluster configuration

SAM is trying to prevent from doing something dumb although you can do it. You simply need to create the LVOL and run newfs from the command line. The "gotcha" is that only the current node knows about the new LVOL so only it will have the dev/vgxx/xxxx device nodes AND only it will have current vgcfgbackup images. The good news is that the critical metadata is stored in the VGRA's of the disks. You can manually create the defvice nodes on the adoptive node(s) BUT you should really run vgcfgbackup on each node (after activating the VG on each adoptive node) otherwise should the disk fail, you can only safely run vgcfgrestore on the current node -- so if the current node fails and you have to replace a disk you could be in heap big trouble.
If it ain't broke, I can fix that.
Rajeev  Shukla
Honored Contributor

Re: Can't create a filesystem in vg that is part of the cluster configuration

You are creating the logical volume without a name, probably that could be the reason SAM can not identify any to create the Filesystem.
The best is to create the lvol and fs using command line options
lvcreate -L 1000 -n lvolname /dev/vg05
newfs -F vxfs /dev/vg05/rlvolname