Creation of new filesystem in vcs environment.

Question

Hi Team,

We have to create a new filesystem and it is in&nbsp;&nbsp;2 node cluster.

/RMPRDR01/oradata5---&gt; Add this new mount point &nbsp;of 252 GB

we have a request to create new filesystem which is in vcs cluster 5.0

For reference about main.cf, attached is the document enclosed.

&nbsp;

df -h
	Filesystem &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; size &nbsp; used &nbsp;avail capacity &nbsp;Mounted on
	/dev/md/dsk/d0 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;15G &nbsp; 9.3G &nbsp; 5.4G &nbsp; &nbsp;64% &nbsp; &nbsp;/
	/devices &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0K &nbsp; &nbsp; 0K &nbsp; &nbsp; 0K &nbsp; &nbsp; 0% &nbsp; &nbsp;/devices
	ctfs &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0K &nbsp; &nbsp; 0K &nbsp; &nbsp; 0K &nbsp; &nbsp; 0% &nbsp; &nbsp;/system/contract
	proc &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0K &nbsp; &nbsp; 0K &nbsp; &nbsp; 0K &nbsp; &nbsp; 0% &nbsp; &nbsp;/proc
	mnttab &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0K &nbsp; &nbsp; 0K &nbsp; &nbsp; 0K &nbsp; &nbsp; 0% &nbsp; &nbsp;/etc/mnttab
	swap &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;34G &nbsp; 1.7M &nbsp; &nbsp;34G &nbsp; &nbsp; 1% &nbsp; &nbsp;/etc/svc/volatile
	objfs &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;0K &nbsp; &nbsp; 0K &nbsp; &nbsp; 0K &nbsp; &nbsp; 0% &nbsp; &nbsp;/system/object
	sharefs &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;0K &nbsp; &nbsp; 0K &nbsp; &nbsp; 0K &nbsp; &nbsp; 0% &nbsp; &nbsp;/etc/dfs/sharetab
	fd &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0K &nbsp; &nbsp; 0K &nbsp; &nbsp; 0K &nbsp; &nbsp; 0% &nbsp; &nbsp;/dev/fd
	/dev/md/dsk/d6 &nbsp; &nbsp; &nbsp; &nbsp; 9.9G &nbsp; 7.5G &nbsp; 2.3G &nbsp; &nbsp;77% &nbsp; &nbsp;/var
	swap &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;36G &nbsp; 2.2G &nbsp; &nbsp;34G &nbsp; &nbsp; 7% &nbsp; &nbsp;/tmp
	swap &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;34G &nbsp; 104K &nbsp; &nbsp;34G &nbsp; &nbsp; 1% &nbsp; &nbsp;/var/run
	swap &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;34G &nbsp; &nbsp; 0K &nbsp; &nbsp;34G &nbsp; &nbsp; 0% &nbsp; &nbsp;/dev/vx/dmp
	swap &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;34G &nbsp; &nbsp; 0K &nbsp; &nbsp;34G &nbsp; &nbsp; 0% &nbsp; &nbsp;/dev/vx/rdmp
	/dev/md/dsk/d9 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;32G &nbsp; 1.9G &nbsp; &nbsp;29G &nbsp; &nbsp; 7% &nbsp; &nbsp;/var/crash
	/dev/odm &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0K &nbsp; &nbsp; 0K &nbsp; &nbsp; 0K &nbsp; &nbsp; 0% &nbsp; &nbsp;/dev/odm
	/dev/vx/dsk/RMPRDR01_ora_data_dg/oratemp
	&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;135G &nbsp; 127G &nbsp; 7.2G &nbsp; &nbsp;95% &nbsp; &nbsp;/RMPRDR01/oratemp
	/dev/vx/dsk/RMPRDR01_ora_data_dg/oradata4
	&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;252G &nbsp; 244G &nbsp; 7.0G &nbsp; &nbsp;98% &nbsp; &nbsp;/RMPRDR01/oradata4
	/dev/vx/dsk/RMPRDR01_ora_data_dg/oradata2
	&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;252G &nbsp; 251G &nbsp; 310M &nbsp; 100% &nbsp; &nbsp;/RMPRDR01/oradata2
	/dev/vx/dsk/RMPRDR01_ora_data_dg/oradata3
	&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;252G &nbsp; 243G &nbsp; 8.3G &nbsp; &nbsp;97% &nbsp; &nbsp;/RMPRDR01/oradata3
	/dev/vx/dsk/RMPRDR01_ora_data_dg/oradata1
	&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;252G &nbsp; 251G &nbsp; 882M &nbsp; 100% &nbsp; &nbsp;/RMPRDR01/oradata1
	/dev/vx/dsk/RMPRDR01_ora_arch_dg/orafra
	&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;107G &nbsp; 5.0G &nbsp; &nbsp;96G &nbsp; &nbsp; 5% &nbsp; &nbsp;/RMPRDR01/orafra
	/dev/vx/dsk/RMPRDR01_ora_arch_dg/oradmp
	&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 67G &nbsp; &nbsp;17G &nbsp; &nbsp;48G &nbsp; &nbsp;26% &nbsp; &nbsp;/RMPRDR01/oradmp
	/dev/vx/dsk/RMPRDR01_ora_bin_dg/oraredo2
	&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 10G &nbsp; 7.9G &nbsp; 1.9G &nbsp; &nbsp;81% &nbsp; &nbsp;/RMPRDR01/oraredo2
	/dev/vx/dsk/RMPRDR01_ora_bin_dg/oraredo1
	&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 10G &nbsp; 7.9G &nbsp; 1.9G &nbsp; &nbsp;81% &nbsp; &nbsp;/RMPRDR01/oraredo1
	/dev/vx/dsk/RMPRDR01_ora_bin_dg/oractl3
	&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;2.0G &nbsp; &nbsp;38M &nbsp; 1.8G &nbsp; &nbsp; 2% &nbsp; &nbsp;/RMPRDR01/oractl3
	/dev/vx/dsk/RMPRDR01_ora_bin_dg/oractl2
	&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;2.0G &nbsp; &nbsp;38M &nbsp; 1.8G &nbsp; &nbsp; 2% &nbsp; &nbsp;/RMPRDR01/oractl2
	/dev/vx/dsk/RMPRDR01_ora_bin_dg/oractl1
	&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;2.0G &nbsp; &nbsp;38M &nbsp; 1.8G &nbsp; &nbsp; 2% &nbsp; &nbsp;/RMPRDR01/oractl1
	/dev/vx/dsk/RMPRDR01_ora_bin_dg/oracle
	&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 20G &nbsp; &nbsp;12G &nbsp; 7.5G &nbsp; &nbsp;62% &nbsp; &nbsp;/RMPRDR01/oracle

====================================================================

vxdisk -o alldgs list &nbsp;o/p -

DEVICE &nbsp; &nbsp; &nbsp; TYPE &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;DISK &nbsp; &nbsp; &nbsp; &nbsp; GROUP &nbsp; &nbsp; &nbsp; &nbsp;STATUS
	c0t0d0s2 &nbsp; &nbsp; auto:none &nbsp; &nbsp; &nbsp; - &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;online invalid
	c0t1d0s2 &nbsp; &nbsp; auto:none &nbsp; &nbsp; &nbsp; - &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;online invalid
	emcpower0s2 &nbsp;auto:cdsdisk &nbsp; &nbsp;emcpowerN17 &nbsp;RMPRDR01_ora_arch_dg online
	emcpower1s2 &nbsp;auto:cdsdisk &nbsp; &nbsp;emcpowerN27 &nbsp;RMPRDR01_ora_data_dg online
	emcpower2s2 &nbsp;auto:cdsdisk &nbsp; &nbsp;emcpowerN28 &nbsp;RMPRDR01_ora_data_dg online
	emcpower3s2 &nbsp;auto:cdsdisk &nbsp; &nbsp;emcpowerN31 &nbsp;RMPRDR01_ora_arch_dg online
	emcpower4s2 &nbsp;auto:cdsdisk &nbsp; &nbsp;emcpowerN34 &nbsp;RMPRDR01_ora_data_dg online
	emcpower5s2 &nbsp;auto:cdsdisk &nbsp; &nbsp;RMPRDR01_ora_bin_dg01 &nbsp;RMPRDR01_ora_bin_dg online
	emcpower6s2 &nbsp;auto:cdsdisk &nbsp; &nbsp;emcpowerN32 &nbsp;RMPRDR01_ora_data_dg online
	emcpower7s2 &nbsp;auto:cdsdisk &nbsp; &nbsp;emcpowerN24 &nbsp;RMPRDR01_ora_data_dg online
	emcpower8s2 &nbsp;auto:cdsdisk &nbsp; &nbsp;emcpowerN26 &nbsp;RMPRDR01_ora_data_dg online
	emcpower9s2 &nbsp;auto:cdsdisk &nbsp; &nbsp;emcpowerN29 &nbsp;RMPRDR01_ora_data_dg online
	emcpower10s2 auto:cdsdisk &nbsp; &nbsp;emcpowerN16 &nbsp;RMPRDR01_ora_arch_dg online
	emcpower11s2 auto:cdsdisk &nbsp; &nbsp;emcpowerN30 &nbsp;RMPRDR01_ora_arch_dg online
	emcpower12s2 auto:cdsdisk &nbsp; &nbsp;emcpowerN33 &nbsp;RMPRDR01_ora_data_dg online
	emcpower15s2 auto:cdsdisk &nbsp; &nbsp;emcpowerN35 &nbsp;RMPRDR01_ora_data_dg online
	emcpower16s2 auto:cdsdisk &nbsp; &nbsp;emcpowerN23 &nbsp;RMPRDR01_ora_data_dg online
	emcpower44s2 auto:cdsdisk &nbsp; &nbsp;emcpowerN19 &nbsp;RMPRDR01_ora_data_dg online
	emcpower45s2 auto:cdsdisk &nbsp; &nbsp;emcpowerN20 &nbsp;RMPRDR01_ora_data_dg online
	emcpower46s2 auto:cdsdisk &nbsp; &nbsp;emcpowerN21 &nbsp;RMPRDR01_ora_data_dg online
	emcpower47s2 auto:cdsdisk &nbsp; &nbsp;emcpowerN22 &nbsp;RMPRDR01_ora_data_dg online
	emcpower50s2 auto:cdsdisk &nbsp; &nbsp;emcpowerN25 &nbsp;RMPRDR01_ora_data_dg online

===========================================================================
	vxassist -g RMPRDR01_ora_data_dg maxsize
	Maximum volume size: 963203072 (470314Mb)

We have a free size available in RMPRDR01_ora_data_dg to 459.29 GB&nbsp;

as the system is in cluster&nbsp;

============================================================================

hastatus -summ

-- SYSTEM STATE
	-- System &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; State &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Frozen

A &nbsp;francona &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; RUNNING &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;0
	A &nbsp;lackey &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; RUNNING &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;0

-- GROUP STATE
	-- Group &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; System &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Probed &nbsp; &nbsp; AutoDisabled &nbsp; &nbsp;State

B &nbsp;MODELN_RPT &nbsp; &nbsp; &nbsp;francona &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Y &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;N &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; OFFLINE
	B &nbsp;MODELN_RPT &nbsp; &nbsp; &nbsp;lackey &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Y &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;N &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ONLINE

&nbsp;

Kindly assist the steps to create a new filesystem, as in this request,
	/RMPRDR01/oradata5---&gt; Add this new mount point &nbsp;of 252 GB.

Let me know if any other info required.

gaurav_s · Answer

Hi,

Replied to your other post ..

https://www-secure.symantec.com/connect/forums/new-filesystem-creation-vxvm#comment-11241041

Refer the FS creation steps in above thread ..

Additionally for VCS here, you need to create Mount resource for this new filesystem &amp; you need to set dependencies (link resources)

to add resource in VCS, open VCS java GUI or VOM if you have, to add via command line, see below

# haconf -makerw

# hares -add &lt;resource_name&gt; Mount MODELN_RPT

# hares -modify&nbsp;&lt;resource_name&gt;&nbsp;BlockDevice /dev/vx/dsk/&lt;diskgroup&gt;/&lt;volume_name&gt;

# hares -modify&nbsp;&lt;resource_name&gt;&nbsp;MountPoint &lt;Mount_Point&gt;

# hares -modify&nbsp;&lt;resource_name&gt;&nbsp;FSType &lt;FS_Type&gt;&nbsp;&nbsp; (vxfs /ufs )

# hares -modify&nbsp;&lt;resource_name&gt; FsckOpt &lt;option&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (-y or -n )

# hares -link &lt;parent_res&gt; &lt;child_res&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;

If mount depends on any resource, then Mount will be parent to that resource, if other resources are depending on Mount, then Mount will be child resource ..

Once linking is done, save the config

# haconf -dump -makero

You can provide more optional attributes if you need, refer here for options

https://sort.symantec.com/public/documents/sfha/6.2/solaris/productguides/html/vcs_bundled_agents/ch02s07s05.htm

&nbsp;

G

&nbsp;

allaboutunix · Answer

Hi Team,

&nbsp;

I am proceeding with the activity for the below filesystem creation in vcs, But Do we require downtime for it.

For checking the failover and switchover, task.

FYI: Class A apps is hosted on it.

mikebounds · Answer

You don't need down time to add filesystem. &nbsp;No need to check failover, especially as there is existing space in the diskgroup (if you would have had to add a new disk, then you would just need to check the disk could be seen by both system, but still wouldn't really be necessary to test failover)

Make sure you create mount point on both nodes in the cluster.

For the safest way to add to cluster I would do in the following order so typos in the hares command (or in GUIs)&nbsp;do not make cluster failover:

Add filesystem in Volume Manager
	Create mount point on both nodes.
	Create resource in VCS, but dont enable or link
	Make resource non-critical
	Enable resource
	Online resource
	Once resource has onlined sucessfully, make resource critical and create resource dependencies.

Mike

Forum Discussion

Creation of new filesystem in vcs environment.

Related Content

new filesystem creation

New filesystem creation in vxvm

MSDP creation error.

Linux Filesystem Backups with ALL_LOCAL_DRIVES

System Recovery 18 - SRD creation and VC Redist