Forum Discussion

symsonu's avatar
symsonu
Level 6
9 years ago

CFSmount is going faulty on second node

Hello friends,

 

CFSmount resource is going faulty and is throwing below erro while coming online... I am not able to mount it manuallly


2016/09/27 07:13:02 VCS NOTICE V-16-1-10301 Initiating Online of Resource cfsmount11 (Owner: Unspecified, Group: vrts_vea_cfs_int_cfsmount11) on System secaprodsnas_02
2016/09/27 07:13:02 VCS WARNING V-16-20011-5502 (secaprodsnas_02) CFSMount:cfsmount11:online:Mount Failed on this Node MountOptions -t vxfs -o cluster,cluster,mntlock=VCS                 Block Device /dev/vx/dsk/sfsdg/esppool-appdata_-05 : MountPoint /vx/esppool-appdata_-05
2016/09/27 07:13:03 VCS WARNING V-16-20011-5508 (secaprodsnas_02) CFSMount:cfsmount11:online:Mount Error : UX:vxfs mount.vxfs: ERROR: V-3-21264: /dev/vx/dsk/sfsdg/esppool-appdata_-05 is already mounted, /vx/esppool-appdata_-05 is busy,
                 or the allowable number of mount points has been exceeded.

No full fsck flag set :-->


secaprodsnas_02:/var/VRTSvcs/log #  echo "8192B.p S" | fsdb -t vxfs /dev/vx/rdsk/sfsdg/esppool-appdata_-05 | grep flag
flags 0 mod 0 clean 3c
secaprodsnas_02:/var/VRTSvcs/log #

Not mounted :-->

 


secaprodsnas_02:/var/VRTSvcs/log # df -h | grep -i -appdata_-05
secaprodsnas_02:/var/VRTSvcs/log # cat /etc/mtab | grep -i -appdata_-05


Could you pleased suggest me the way forward ?

 

I have recreated the mount point as well.

Regards

Sumit

  • Dev_Roy's avatar
    Dev_Roy
    Level 6
    9 years ago

    What is the OS and Veritas version?

    Did you try fuser to determine if any process or user is trying to access the file system?

    Did you try unmounting and mounting outside of Veritas?

     

    • symsonu's avatar
      symsonu
      Level 6
      9 years ago

      Its suse linux 11 and veritas 5.1

       

      yes fuser didnot report anything

      I tried mount outside of veritas ..giving same error

       

       

      • Dev_Roy's avatar
        Dev_Roy
        Level 6
        9 years ago

        Then clearly VCS is victim and not culprit in this case.

        Give me below command output:

        df -h

        umount -f /<mount point>

        df -h

        vxprint -qhtrg <dg name>

        rpm -qa | grep - i vrtsvcs

        rpm -qa | grep - i vrtsvxfs

        gabconfig -a

        vsdctl -c mode

        Was it working before? Was there any changes on the system in the recent past?