"ERROR: V-3-21268: /dev/vx/dsk/diskgroup/volume is corrupted. needs checking" is reported by Storage Foundation, suggesting filesystem corruption within a VxFS volume

book

Article ID: 100009174

calendar_today

Updated On:

Description

Error Message

Error : UX:vxfs mount: ERROR: V-3-21268: /dev/vx/dsk/disk group/volume is corrupted. needs checking

Table of Contents


1. Introduction
2. Gathering information about the file system, including a metasave
3. Replaying a metasave





1. Introduction

(Back to top)


When VxFS file system corruption is suspected, the degree of corruption can be often assessed *before* attempting to run “fsck –y."

Note: Once "fsck -y" has been performed, permanent changes to the metadata have already occurred.  As a result, further analysis of the file system is unlikely to be productive.





2. Gathering a metasave, and other information about the file system

(Back to top)


Gathering a "metasave" of the filesystem, along with other information, makes it possible to safely run fsck against a "replay" of the filesystem metadata instead of running it against actual production data. This can be used to "predict" the effect that running fsck -y will have on a file system without actually running it on production data.
 


Steps for gathering a metasave, and other information about the file system are available at How to collect the file system metadata, and other information, in the event of possible VxFS file system corruption


 

 




3. Replaying a Metasave

(Back to top)


The benefit of replaying a metasave on a temporary volume is that it allows the use of utilities that affect file system metadata, such as fsck and fsdb, without affecting the original file system.
 


Steps for replaying a metasave can be found here at How to replay a metasave of a VxFS file system by using a sparse volume


 


 

 

 

 

Resolution


Issue/Introduction

This article discusses how to troubleshoot VxFS filesystem corruption.
 

Additional Information

UMI: V-3-21268