If a volume is unmounted during a "Subdisk Move" operation; the task may complete abnormally, resulting in the volume reporting data corruption and may report the Filesystem as RAW

If a volume is unmounted during a "Subdisk Move" operation; the task may complete abnormally, resulting in the volume reporting data corruption and may report the Filesystem as RAW

Article: 100028756
Last Published: 2013-11-07
Ratings: 0 0
Product(s): InfoScale & Storage Foundation

Problem

If a volume is unmounted during a 'Subdisk Move' operation with the SmartMove feature enabled, the task may complete abnormally resulting in the volume reporting file corruption, and/or the volume showing as RAW. A volume can be unmounted in 2 different ways: 

- The MountV resource (Veritas Cluster Server) or Volume Manager Disk Group resource (Windows Failover Cluster) in the cluster is taken offline
- The Drive Letter or Drive Path is manually removed from the volume
 

Workaround:
The SmartMove feature can be disabled as a workaround to this issue. Follow the steps provided below to disable SmartMove:

1. Open the Veritas Enterprise Administrator (VEA) console.
2. Select the 'Control Panel' option from the far left pane.
3. Select the 'System Settings' icon from the far right pane (double-click)
4. Select the SmartMove tab.
5. Uncheck the 'Enable SmartMove' option

SmartMove: The performance of mirror operations and subdisk moves can be enhanced with the SmartMove feature. SmartMove helps reduce the resynchronization time required by mirror operations and subdisk moves. The resynchronization time is reduced by using the NTFS file system metadata to resynchronize only selected regions. With this feature disabled, 'Subdisk Move', and 'Mirror Creation/Resynchronization' operations may take longer to complete.

Solution

This issue has been resolved in all the 6.0.x and and 5.1 Sp2 versions of Storage Foundation for Windows

5.1 Sp2:

A publicly available fix has been made available for this version of the product: https://sort.veritas.com/patch/detail/8071.

This fix will be included in Cumulative Patches 20 (CP 20) for 5.1 Sp2.

6.0:

This fix is included in CP 5 for 6.0 and will be included in all future CP releases for the 6.0 product. To find the available CP; please see the following article: https://www.veritas.com/docs/000016920.

Note: This article provides links to the latest CP and includes a separate link for each product (SFW and SFW-HA). Be sure to choose the proper CP download for the product installed on the server. 

6.0.1:
A publicly available fix has been made available for this version of the product: sort.veritas.com/patch/detail/7284.

This fix has also been included in CP 1 for 6.0.1 and all later CP releases for the 6.0.1 product.  To find the latest available CP; please see the following article: https://www.veritas.com/docs/000018682.

6.0.2:

A publicly available fix has been made available for this version of the product: sort.veritas.com/patch/detail/7781.

 

 

References

Etrack : 3319824 Etrack : 3082932 Etrack : 3017937 Etrack : 3207622

Was this content helpful?