new filesystem creation

Hi, 

 Try:

1.  vxassist -g ora_datadg  make  wind_index1 91g

2. mkfs -F vxfs  /dev/vx/rdsk/ora_datadg/wind_index1 

  if it's AIX , need use mkfs -V, if it's linux, need user mkfs -t

3. mkdir /wind_index1

4. mount -F vxfs /dev/vx/dsk/ora_datadg/wind_index1 /wind_index1

  if it's AIX , need use  -V, if it's linux, need user  -t  instead of -F

if need add to vcs, need more actions.

Regards

When I checekd teh vfstab configuration these filesystems are not available.

But, when I checked in main.cf it shows like that

Mount mnt_wind_blobs2 (
                MountPoint = "/wind_blobs2"
                BlockDevice = "/dev/vx/dsk/ora_datadg/wind_blobs2"
                FSType = vxfs
                FsckOpt = "-y"
                )

        Mount mnt_wind_index (
                MountPoint = "/wind_index"
                BlockDevice = "/dev/vx/dsk/ora_datadg/wind_index"
                FSType = vxfs
                FsckOpt = "-y"
                )

        Mount mnt_wind_oraarchive (
                MountPoint = "/wind_oraarchive"
                BlockDevice = "/dev/vx/dsk/ora_archdg/wind_oraarchive"
                FSType = vxfs
                FsckOpt = "-y"
                )

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

Disks are auto and not shared 

root@lyle# vxdg list
NAME         STATE           ID
oradg        enabled              1145631633.68.lupien
appdg        enabled              1135802559.341.lupien
ora_archdg   enabled              1145635551.78.lupien
ora_datadg   enabled              1145636901.92.lupien
vaultdg      enabled              1135801061.265.lupien

In this condition how to proceed?

Do steps as above:

1.  vxassist -g ora_datadg  make  wind_index1 91g

2. mkfs -F vxfs  /dev/vx/rdsk/ora_datadg/wind_index1 

  if it's AIX , need use mkfs -V, if it's linux, need user mkfs -t

3. mkdir /wind_index1

Then create resource in VCS in Java GUI (you can copy and paste an existing resource and change attributes) or from CLI:

hares -add Mount mnt_wind_index1 sg_name
hares -modify mnt_wind_index1 MountPoint /wind_index
hares -modify mnt_wind_index1  BlockDevice /dev/vx/dsk/ora_datadg/wind_index
hares -modify mnt_wind_index1  FSType vxfs
hares -modify mnt_wind_index1  FsckOpt %-y
hares -modify mnt_wind_index1  Critical 0 
hares -modify mnt_wind_index1  Enabled 1

Then online resource
 hares -online mnt_wind_index1  -sys system

Confirm is online:

 hares -state mnt_wind_index1 

hen make critical (you make non-critical earlier in case there are any typos in resource)

hares -modify mnt_wind_index1  Critical 1

Then link to diskgroup resource

hares -link mnt_wind_index1  dg_res_name

Mike

I checked and found that Disks of this diskgroup is not  located on shared storage.

root@lyle# vxdisk list |grep -i ora
emcpower86s2 auto:simple     oradg02      oradg        online thin
emcpower87s2 auto:simple     oradg01      oradg        online thin
emcpower88s2 auto:simple     ora_datadg01  ora_datadg   online thin
emcpower89s2 auto:simple     ora_datadg02  ora_datadg   online thin
emcpower90s2 auto:simple     ora_datadg07  ora_datadg   online thin
emcpower91s2 auto:simple     ora_datadg05  ora_datadg   online thin
emcpower92s2 auto:simple     ora_datadg03  ora_datadg   online thin
emcpower93s2 auto:simple     ora_datadg04  ora_datadg   online thin
emcpower94s2 auto:simple     ora_datadg08  ora_datadg   online thin
emcpower95s2 auto:simple     ora_datadg06  ora_datadg   online thin
emcpower96s2 auto:simple     ora_archdg01  ora_archdg   online thin

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

root@lyle# vxdg list ora_datadg
Group:     ora_datadg
dgid:      1145636901.92.lupien
import-id: 1024.167
flags:
version:   110
alignment: 8192 (bytes)
ssb:            on
autotagging:    off
detach-policy: global
dg-fail-policy: invalid
copies:    nconfig=default nlog=default
config:    seqno=0.2551 permlen=48346 free=48306 templen=19 loglen=7325
config disk emcpower88s2 copy 1 len=48346 state=clean online
config disk emcpower89s2 copy 1 len=48346 state=clean online
config disk emcpower90s2 copy 1 len=48346 state=clean online
config disk emcpower91s2 copy 1 len=48346 disabled
config disk emcpower92s2 copy 1 len=48346 disabled
config disk emcpower93s2 copy 1 len=48346 disabled
config disk emcpower94s2 copy 1 len=48346 state=clean online
config disk emcpower95s2 copy 1 len=48346 state=clean online
log disk emcpower88s2 copy 1 len=7325 disabled
log disk emcpower89s2 copy 1 len=7325
log disk emcpower90s2 copy 1 len=7325
log disk emcpower91s2 copy 1 len=7325
log disk emcpower92s2 copy 1 len=7325
log disk emcpower93s2 copy 1 len=7325 disabled
log disk emcpower94s2 copy 1 len=7325
log disk emcpower95s2 copy 1 len=7325 disabled

This seems that diskgroup is not shared.

Shall i proceed with the above suggested steps even if diskgroup is not shared?

Please assist.

Who will be the parent and child resource  to link, in this condition?

Please reply to the above query as soon as possible as i have to perform this activity.

I humbly request you to suggest on this.I did not receive reply since two days.

thanks. 

1. It's normal not in vfstab, but in main.cf.

2. for failover file system, dg should only import in one server, dg shouldn't in share sate.

When you need urgent assistance over a weekend, it is best to log a Support call with Symantec.

All of us trying to assist here (including Symantec employees) are doing so in our own time.

When you have disk storage in a 'normal' failover cluster (not CVM/CFS) you need to list disks in a diskgroup with this command on both nodes:

vxdisk -o alldgs list 
(you can pipe the output to |grep ora_datadg)

With above output, you will see that the disks will be seen by both nodes, but only imported on one node. 
The node where the diskgroup and SG is deported/offline, will show the diskgroup in brackets in vxdisk output.

So, in a failover cluster, shared disks are seen by both nodes, but can only be imported (online) on one node.