03-17-2015 08:53 AM
Hi all,
I've found a problem after create a resource to mount ext3 device.
Mount dNFS_Mount (
MountPoint = "/share"
BlockDevice = vg_fs_cal-lv_fs_cal
FSType = ext3
MountOpt = noatime
FsckOpt = "-y"
)
In fact the vg_fs_cal-lv_fs_cal exists if i activate the Vg using,
vgchange -ay vg_fs_cal
I can do it manually but veritas cant mount it and the resource always fail.
What can i Check, the log only show this, but if list the device exits
Mount:dNFS_Mount:online:Block device vg_fs_cal-lv_fs_cal does not exist
What can i check? What is wrong in device creation?
Solved! Go to Solution.
03-17-2015 10:21 AM
The BlockDevice attribute needs to be a full pathname, such as "/dev/mapper/ora_vg-ora_vol" ; so in your case maybe something like "/dev/mapper/vg_fs_cal-lv_fs_cal"
03-17-2015 10:21 AM
The BlockDevice attribute needs to be a full pathname, such as "/dev/mapper/ora_vg-ora_vol" ; so in your case maybe something like "/dev/mapper/vg_fs_cal-lv_fs_cal"
03-17-2015 10:23 AM
FYI: You really ought to give us your OS release level and SFHA level as well.
03-17-2015 07:55 PM
Always a good idea to download the Bundled Agent Guide for your VCS version.
This is what the 6.0 guide says about BlockDevice attribute in Mount agent:
For LVM2, use the actual mapper path to the volume.
Type and dimension: string-scalar
Examples:
■ LVM2 example
# ls -la /dev/ora_vg/ora_vol
lrwxrwxrwx 1 root root 26 Apr 17 04:48
/dev/ora_vg/ora_vol -> /dev/mapper/ora_vgora_vol
Use the path /dev/mapper/ora_vg-ora_vol for the BlockDevice attribute.
■ NFS example
If the file system type is NFS, then specify the BlockDevice as:
server:/path/to/share
galaxy.symantecexample.com:/usr/share1
■ "/dev/vx/dsk/myvcs_dg/myvol"
■ IPv6
"[fe80::1:2:3]:/dirname/anotherdir"
You can download manuals for your version over here:
https://sort.symantec.com/documents