Update in Infoscale 7.4.1u3 introduced additional logging for VVR in /var, and can fill up /var partition quickly.

Description

As of Infoscale 7.4.1u3, additional logging was added for VVR (Veritas Volume Replicator) in /var, and can fill /var to 100% very quickly.

New file:

/var/adm/vx/rp_rv.log

If not carefully monitored and addressed, /var filling up can cascade into other issues, possibly affecting server and application stability.

Action Required

To disable VVR from logging this extra information, use "vxtune" to set the value of the vol_log_category. This does not require a reboot, and will be persistent. However, this change is on a per-node basis only - this step will need to be performed by any affected members of the cluster or source/target of the replication.

// Display current value:

server01:/ # vxtune vol_log_category

Tunable                                        Current Value                Default Value Reboot Clusterwide

-------------------------------                -------------                ------------- ------ -----------

vol_log_category                fmr,vvr,base,ted,smartio,cvm fmr,vvr,base,ted,smartio,cvm    N        N

// Remove "vvr," from the current values:

server01:/ # vxtune vol_log_category fmr,base,ted,smartio,cvm

// Display newly set value:

server01:/ # vxtune vol_log_category

Tunable                                        Current Value                Default Value Reboot Clusterwide

-------------------------------                -------------                ------------- ------ -----------

vol_log_category                    fmr,base,ted,smartio,cvm fmr,vvr,base,ted,smartio,cvm    N        N

Note: Using vxtune to remove "vvr" from the vol_log_category parameter can impact analysis of errors, as we are not logging VVR kernel messages to /var.

10KB of log data is still kept in the kernel, and can be extracted as needed for engineering analysis.

Issue/Introduction

As of Infoscale 7.4.1u3, additional logging was added for VVR (Veritas Volume Replicator) in /var, and can fill /var to 100% very quickly. New file: /var/adm/vx/rp_rv.log If not carefully monitored and addressed, /var filling up can cascade into other issues, possibly affecting server and application stability.

Action Required

To disable VVR from logging this extra information, use "vxtune" to set the value of the vol_log_category. This does not require a reboot, and will be persistent. However, this change is on a per-node basis only - this step will need to be performed by any affected members of the cluster or source/target of the replication. // Display current value:

server01:/ # vxtune vol_log_category

Tunable                                        Current Value                Default Value Reboot Clusterwide

-------------------------------                -------------                ------------- ------ -----------

vol_log_category                fmr,vvr,base,ted,smartio,cvm fmr,vvr,base,ted,smartio,cvm    N        N

// Remove "vvr," from the current values:

server01:/ # vxtune vol_log_category fmr,base,ted,smartio,cvm

// Display newly set value:

server01:/ # vxtune vol_log_category

Tunable                                        Current Value                Default Value Reboot Clusterwide

-------------------------------                -------------                ------------- ------ -----------

vol_log_category                    fmr,base,ted,smartio,cvm fmr,vvr,base,ted,smartio,cvm    N        N

Note: Using vxtune to remove "vvr" from the vol_log_category parameter can impact analysis of errors, as we are not logging VVR kernel messages to /var.
10KB of log data is still kept in the kernel, and can be extracted as needed for engineering analysis.

Additional Information

JIRA: IIP-32441

Welcome to "KB Articles"