cancel
Showing results for 
Search instead for 
Did you mean: 

corrupted veritas file system

Dear Support

I am facing the below issue whenever running the fsck,please find the below details---

****************************************************************************************************

[10:40am] root@dwse: # /opt/VRTS/bin/fsck -F vxfs /dev/vx/rdsk/storagedg/vardws_vol
UX:vxfs fsck: ERROR: V-3-20005: read of super-block on /dev/vx/rdsk/storagedg/vardws_vol failed: No such device or address
file system check failure, aborting ...
Exit 1
 
Exit 34
[10:43am] root@dwse: # /opt/VRTS/bin/fsck -F vxfs /dev/vx/rdsk/storagedg/varoptbgw_vol
UX:vxfs fsck: ERROR: V-3-20005: read of super-block on /dev/vx/rdsk/storagedg/varoptbgw_vol failed: No such device or address
file system check failure, aborting ...
Exit 1
[10:44am] root@dwse: #
 
*********************************************************************
Due to which volumes cannot be able to mount,kindly suggest what need to do/
 
 
regards....Arup
1 Solution

Accepted Solutions
Accepted Solution!

Maybe the volume or subdisks

Maybe the volume or subdisks were disabled due to an intermittent error.

Next time you should check syslogs, vxprint, vxdisk output and the dmpevents log.

What can also happen is that you added/removed LUNs which triggered a re-enumeration of the OS devices so that the DMP devices nodes were pointing to the wrong or non existent OS devices

View solution in original post

8 Replies

Moved to correct forum (from

Moved to correct forum (from Storage and Clustering Documentation to Storage Foundation)

In the meantime, please provide the following output:

# vxprint -qhtrg storagedg

# vxdisk -o alldgs list

Hi Everyone The issue got

Hi Everyone

The issue got resolved,after rebooting the server,what it did during rebooting fsck runs & checks the fs for any error.After checking it make the fs as clean.

 

 

regards...Arup

No such device or

No such device or address 

This means that the devices were not present at OS level.

The reboot then detected the disk devices resulting in successful fsck.

No, devices were present in

No, devices were present in the OS as the concerned DG is showing enabled & also the corresponding volumes from the DG are showing active & enabled in the vxprint output. Still the VXVM fsck was not running & giving the above mentioned error.Finally we have to reboot the server.

Accepted Solution!

Maybe the volume or subdisks

Maybe the volume or subdisks were disabled due to an intermittent error.

Next time you should check syslogs, vxprint, vxdisk output and the dmpevents log.

What can also happen is that you added/removed LUNs which triggered a re-enumeration of the OS devices so that the DMP devices nodes were pointing to the wrong or non existent OS devices

View solution in original post

Thank you Daniel for your

Thank you Daniel for your suggestion.What is the exact location of the dmpevents log. 

Hi Arup,   it's in

Hi Arup,

 

it's in /etc/vx

 

Please see belwo link for details:

http://sfdoccentral.symantec.com/sf/5.1SP1/linux/html/dmp_admin/ch06s04.htm

 

If the error is saying "no

If the error is saying "no such device or address" that means the volume device itself was not existing in /dev/vx/rdsk/storagedg/  directory.

One thing I would be interested to know is, whether all the volumes in this DG faced the same error or there were some working (serving I/O) to filesystems were existing ? Any recent deport/import operations happened ?

If in case, all the volumes had issues, I would also suspect that the DG itself had issues or somehow vxio or vxconfigd was unable to talk to DG leaving it in stale state. This would also trigger a pointer to know if there were any storage issues during the same time (any errors observed in /var/adm/messages file ?)

If above isn't the case (i.e some volumes were working), then did someone manually deleted the block device files from /dev/vx/rdsk/storagedg/  directory ?

 

G