Error Message

vxfs: msgcnt 13 mesg 167: V-2-167: Permission denied for Inode 5 on filesystem /dev/vx/dsk/sfsdg/testvol uid 3003 gid 3007 failed with error 13

Starting at VRTSvxfs patch 8.0.0.1800 a new tunable was introduced eo_logging_enable.

To enable the tunable on a filesystem (in this example, mountpoint /testvol ):
# vxtunefs -o eo_logging_enable=1 /testvol/

To disable the tunable on a filesystem:
# vxtunefs -o eo_logging_enable=0 /testvol/

The tunable can be permanently enabled or disabled by adding an entry to /etc/vx/tunefstab.
For example, to enable the tunable on all VxFS mountpoints
system_default eo_logging_enable=1

When this tunable is enabled, VxFS will log messages in syslog whenever any user attempts to access any file in a way which violates the permissions of that file.

The uid  (User ID) and gid (Group ID) of the user are given along with the inode number of the file and which volume the filesystem is mounted on.

The message does not indicate any error or problem with VxFS itself. VxFS is only logging the fact that a user attempted to access a file in a way which violates the permissions of that file.

The username and group of the user can be found using the command id
The inode number can be found using command vxlsino

Using the above message as an example, we can find the user is 'testuser2' and the group is 'testuser2'

# id 3003
uid=3003(testuser2) gid=3007(testuser2) groups=3007(testuser2)

To find the file, we must first find the mountpoint used for the device specified

# mount | grep /dev/vx/dsk/sfsdg/testvol
/dev/vx/dsk/sfsdg/testvol on /testvol type vxfs (rw,delaylog,largefiles,ioerror=mwdisable)

We can now use vxlsino to find the file associated with the inode number
# vxlsino 5 /testvol
/testvol/testfile2

Therefore, in this example, we know that user 'testuser2' who is in group 'testuser2' attempted to access file /testvol/testfile2 in a way which violated the permissions of the file.

The administrator should examine what the specified user is doing and confirm the ownership and permissions of the file are as required. Then make adjustments as required to ensure the user correctly respects the permissions and ownership of the file.