cancel
Showing results for 
Search instead for 
Did you mean: 

What's the messages ?

 

Hello everyone.

My customer have SFHA5.0MP3RP5 for solaris 8.

I saw the VCS engine log. Here's the messages :

 

Jul 22 15:41:12 ifap1p AgentFramework[4135]: [ID 702911 daemon.notice] VCS ERROR V-16-1-5586 Mount:mnt_oracle:monitor:Mount point /oracle is busy with some other block device.
Jul 22 15:46:12 ifap1p AgentFramework[4135]: [ID 702911 daemon.notice] VCS ERROR V-16-1-5586 Mount:mnt_oracle:monitor:Mount point /oracle is busy with some other block device. 
Jul 22 15:51:13 ifap1p AgentFramework[4135]: [ID 702911 daemon.notice] VCS ERROR V-16-1-5586 Mount:mnt_oracle:monitor:Mount point /oracle is busy with some other block device.
Jul 22 15:56:13 ifap1p AgentFramework[4135]: [ID 702911 daemon.notice] VCS ERROR V-16-1-5586 Mount:mnt_oracle:monitor:Mount point /oracle is busy with some other block device.
Jul 22 16:01:13 ifap1p AgentFramework[4135]: [ID 702911 daemon.notice] VCS ERROR V-16-1-5586 Mount:mnt_oracle:monitor:Mount point /oracle is busy with some other block device.
 
What's is mean the messages ?
I appreciate if any of you can offer me some advice.
1 Solution

Accepted Solutions
Accepted Solution!

Two Mount Resources both mounting at the same mount point?

Does your VCS configuration have two different Mount resources which are both trying to mount a file system (2 different file systems) on the same mount point?  This would cause this error message.

View solution in original post

2 Replies

Need some inputs here .. --

Need some inputs here ..

-- df output for this mountpoint ..

-- main.cf defination for the resource in question ...

-- detail monitoring enabled ?

-- is cluster frozen ?

-- any concurrence violation errors in engine_A.log around same day ?

 

 

G

Accepted Solution!

Two Mount Resources both mounting at the same mount point?

Does your VCS configuration have two different Mount resources which are both trying to mount a file system (2 different file systems) on the same mount point?  This would cause this error message.

View solution in original post