Can't ufsdump; Super-block on device is corrupt...

[stevenriz]

... run fsck

Yes still using ufsdump to backup file systems. We have a new disk (36gb) that when I attempt to dump it, get this message...
-----------------
server3# /usr/sbin/ufsdump 0fu application:/dev/rmt/0n /dev/vx/dsk/directory/vol01
DUMP: Warning - super-block on device `/dev/vx/rdsk/directory/vol01' is corrupt - run fsck
DUMP: The ENTIRE dump is aborted.
-----------------
Via Veritas, I ran the Check and Repair on that mount point and ot the "File system "blablabla" is okay." Well it isn't okay because I continue to get that message. I can't get fsck to work on that file system at all. When I try it, it comes back with...
----------------
server3# fsck f /dev/vx/dsk/directory/vol01
fsck: operation not applicable to FSType nfs
fsck: operation not applicable to FSType nfs
server3#
-----------------
Any clues?

 

[jaSun]

I am not 100% sure about this, but I think that without arguments, the fsck utility expects to see a UFS file system. Also, fsck needs the physical disk names and not the directory name Try something like this instead:

fsck -F vxfs /dev/rdsk/c?t?d?s?

You will need to supply the correct controller, targer, device and slice numbers for the disk used. Try running vxprint as user root in order to cross-reference what filesystems Veritas has placed on what disks.

 

[stevenriz]

Thanks for the reply. I ran vxprint and double checked that with what Veritas shows the physical device to be. They matched so I ran
fsck -F vxfs /dev/rdsk/c0t9d0s2
I received this message.
---
vxfs fsck: not a valid vxfs file system (but it is)
invalid super-block
---
I didn't set this system up so I am trying to get ahold of the person that did. Thanks for the help, if you have any other ideas to try, please let me know. Thank you.

 

[stevenriz]

Thanks for the reply. I ran vxprint and double checked that with what Veritas shows the physical device to be. They matched so I ran
fsck -F vxfs /dev/rdsk/c0t9d0s2
I received this message.
---
vxfs fsck: not a valid vxfs file system (but it is)
invalid super-block
---
I didn't set this system up so I am trying to get ahold of the person that did. Thanks for the help, if you have any other ideas to try, please let me know. Thank you.

 

[bi]

You say in one of your earlier messages you get this error:

server3# fsck f /dev/vx/dsk/directory/vol01
fsck: operation not applicable to FSType nfs
fsck: operation not applicable to FSType nfs
server3#

This error message seems to indicate it is an NFS mounted filesystem. If it is NFS mounted from another server, I don't think you will be able to do an fsck on it from server3. Nor would you be able to do a ufsdump from server3 because it is not a ufs filesystem.

 

[stevenriz]

Thanks for all your replies. My problem was stemmed from using the WRONG command to dump the data. Since this is a vxfs file system, I discovered the vxdump command which works just fine. Damn!!
steve