Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Errors "V-2-96 vx_setfsflags file system full fsck flag set" and "V-2-17 vx_iread_1 file system inode marked bad incore"

Created: 16 Sep 2013 • Updated: 30 Oct 2013 | 1 comment
This issue has been solved. See solution.

Hi All ,

I am getting the above messages from one of the node in VCS. We are running with RHEL 5.8 version.

The messages refering to a particular filesystem is mounted in rw mode, and there was no issues reported except these messages.

I found an article http://www.symantec.com/docs/TECH135425 but states a solution  for Solaris 10 x86 .

Is there any tech doc refering to RHEL also please suggest.  And also is this error critical ????

 

Regards ,

Sourav

Operating Systems:

Comments 1 CommentJump to latest comment

TonyGriffiths's picture

Hi

From the info mentioned, it would appear that VxFS encountered an error whilst processing an inode and marked it bad. Furthermore it has determined that a full fsck (structural check) is required and has set the flag so that when it next goes through a fsck, a full will be required as opposed to the quick log replay.

As for the reason why this occured, that is unkown, it could be that the data it read form disk was invalid.

You should check syslog for any evidence of other storage or vxfs messages. Also ensure you have a valid backup.

 

cheers

tony

SOLUTION