fstyp - read of super-block failed

[Glen Trevino]

When trying to get info on some lvols using fstyp, I got the following:

# fstyp -v /dev/vg01/lvol56
vxfs
read of super-block on /dev/vg01/lvol56 failed: Invalid argument
read of super-block on /dev/vg01/lvol56 failed: Invalid argument

version: 4294967295
f_bsize: 8192
f_frsize: 1024
f_blocks: 4096000
f_bfree: 2030181
f_bavail: 1903551
f_files: 506552
f_ffree: 507544
f_favail: 507544
f_fsid: 1073807414
f_basetype: vxfs
f_namemax: 254
f_magic: a501fcf5
f_featurebits: 0
f_flag: 16
f_fsindex: 7
f_size: 4096000

Is the error something I should be concerned with? This is a L3000 running HP-UX 11i.

[Michael Tully]

It looks like a super block error.

First do some enquiries:

# lvdisplay -v /dev/vg01/lvol56 (and look for the disks being used as well as any other errors.

# pvdisplay -v /dev/dsk/cxtytdz (and look for stale extents)

test the disk
# dd if=/dev/dsk/cxtydz of=/dev/null bs=2048k

Run an fsck on the filesystem
# fsck -F vxfs -o full /dev/vg01/lvol56

Look for errors relating to the disk in the syslog. This will probably confirm if it is a dodgy disk. Make sure your backups are up to date, if there is no alternate disk protection.

[Tim Adamson_1]

I agree with Michael. Run an fsck on the filesystem. Also check for errors in syslog.log.


Tim

[Glen Trevino]

I've already did the preliminary checks for stale extents (we run scripts from cron to check for stale extents every 30 minutes) and disk errors. Unfortunately, I can't do a fsck on it at the moment because there is a production application using that lvol and I can't unmount it right now. Also no errors in the syslog...