Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.

Dell EMC Solutions Enabler 9.2 SRDF Family CLI User Guide

Check for R1 invalid tracks

Under normal operations, the symrdf verify -consistent command verifies that SRDF device pairs are in the R2 Consistent pair state. No invalid tracks are owed to the R2 side from its R1 side.

When an SRDF pair is in the Split state and the host writes to its R2 device, invalid tracks are owed to its R1 device.

Once the pair is restored, the pair is still in the Consistent state because no invalid tracks are owed to the R2 device. SRDF does not recognize invalid tracks owed from R2 to R1.

The symrdf verify command with -noinvalids and -consistent options performs an additional check to verify whether invalid tracks exist on both the R1 and R2 devices.

Syntax

Use the symrdf verify command with -noinvalids and -consistent options to verify invalid tracks on device groups, composite groups, storage groups, and device files.

symrdf verify -g Dgname -consistent -noinv 
symrdf verify -cg Cgname -consistent -noinv
symrdf verify -sg SgName -consistent -noinv 
symrdf verify -file Filename -consistent -noinv 

Example

To monitor the clearing of invalid tracks every 60 seconds for the device group dg1 :

symrdf verify -g dg1 -consistent -noinv -i 60


None of the devices in the group 'dg1' are in 'Consistent with no invalid tracks' state.

Not all devices in the group 'dg1' are in 'Consistent with no invalid tracks' state.

All devices in the group 'dg1' are in 'Consistent with no invalid tracks' state.

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\