Trying to mount a LV: after do a fsck I get "vxfs fsck: not a valid vxfs file system"

[Daniel_RP]

Hi all,

I tried to mount a lv, but I receive next error:

Command:
#/usr/sbin/fsck /dev/vgHITACHI_SI_6/lvHIP17


Error:
fsck: /etc/default/fs is used for determining the file system type
vxfs fsck: not a valid vxfs file system
vxfs fsck: cannot initialize aggregate
invalid super-block file system check failure, aborting ...


Doing: #lvdisplay /dev/vgHITACHI_SI_6/lvHIP17

I receive:
lvdisplay: Volume group "/dev/vgHITACHI_SI_6" does not exist in the "/etc/lvmtab" file.
lvdisplay: Cannot display logical volume "/dev/vgHITACHI_SI_6/lvHIP17".


#ll /dev/vgHITACHI_SI_6
total 0
crw-rw-rw- 1 root sys 64 0x430000 Dec 18 11:23 group
brw------- 1 root sys 64 0x430001 Dec 20 10:12 lvHIP16
brw------- 1 root sys 64 0x430002 Dec 20 10:12 lvHIP17
brw------- 1 root sys 64 0x430003 Dec 20 10:13 lvHIP18
crw------- 1 root sys 64 0x430001 Dec 20 10:12 rlvHIP16
crw------- 1 root sys 64 0x430002 Dec 20 10:12 rlvHIP17
crw------- 1 root sys 64 0x430003 Dec 20 10:13 rlvHIP18

If I do: #lvcreate –L 31984 –n lvHIP17 /dev/vgHITACHI_SI_6

I lose information but I can mount the LV.

After Shadow Image copy (SAN) do a copy on this disk I receive same error and I can't mount again.


Any idea?

Thanks in advance.

[Asif Sharif]

Hi alvarez,

Please see the below thread.

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=61799
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1065329

Regards,
Asif Sharif

[Daniel_RP]

Sorry, mistake, in last point I do:

newfs -F vxfs -o largefiles /dev/vgHITACHI_SI_6/rlvHIP17

(Instead of lvcreate -L 31984 ... )

[Daniel_RP]

Sorry, mistake, in last point I want say:

#newfs -F vxfs -o largefiles /dev/vgHITACHI_SI_6/rlvHIP17

(Instead of lvcreate -L 31984 ... )

[Daniel_RP]

Hi, Sharif

I think that my case does not in none of this two situations.

[Ganesh Balraman]

Dear Sir,

This related to superbolck error,

Try to run the fsck in alternate superblock by specifying fsck -b .

Alternate superblock can be found in /var/adm/sbtab.

This could sort out the issue.

Regds
B.Ganesh

[Sandman!]

Are you sure that this is a vxfs filesystem? Try running fsck with the filesystem type option given explicitly on the command line i.e.

# /usr/sbin/fsck -F vxfs /dev/vgHITACHI_SI_6/lvHIP17

[Daniel_RP]

Hi Ganesh,

I don't have directory /var/adm/sbtab.

I tried to run the fsck -b and get: "
fsck: illegal option -- b
vxfs fsck: Usage:
fsck [-V] [-F vxfs] [-pmnNyY] [-o full,nolog] special"


To Sandman, I tried to do a /usr/sbin/fsck -F vxfs /dev/vgHITACHI_SI_6/lvHIP17, but I got this error:

"vxfs fsck: not a valid vxfs file system
invalid super-block
vxfs fsck: cannot initialize aggregate
file system check failure, aborting ..."


At the moment unique method to exit from this situation is making a newfs and loosing all information. After do this, I can mount, but as soon as I run another disk copy.

Surprising that from 3 new LV created, one preserves the config and can mount after Shadow Image copy (HITACHI SAN), and other 2 have this problem. I created all three with same pattern.

/dev/vgHITACHI_SI_6/rlvHIP16--> OK
/dev/vgHITACHI_SI_6/rlvHIP17--> KO
/dev/vgHITACHI_SI_6/rlvHIP18--> KO

Any idea?

Thanks.

[Georgi Enev]

Hi
Could yoy check version of your fschk !
Find and use appropriatle version.

luck

[Sunny Jaisinghani]

hi

try running vgscan so that any issues with the /etc/lvmtab are resolved. then u can try fsck again.

[A. Clay Stephenson]

After you run your lvcreate and restore the shadow image then execute fstyp -v /dev/vgxx/lvolyy and that will tell if there is a filesystem on the LVOL and what kind of filesystem that it is.

[Daniel_RP]

What can I do to have same "USED PV" in two vg's from diferent machines?

Why "USED PV" are diferent? They are formed by 4 disks in two cases, 4 disks with the same capacity.


Source Machine:

LV Name /dev/vgHITACHI_P6/lvHIP18
LV Status available/syncd
LV Size (Mbytes) 31984
Current LE 7996
Allocated PE 7996
Used PV 4

Destination machine:

LV Name /dev/vgHITACHI_SI_6/lvHIP18
LV Status available/syncd
LV Size (Mbytes) 31984
Current LE 7996
Allocated PE 7996
Used PV 2


It could cause the talked error?

Thanks.

[Daniel_RP]

Hi Clay,


root@xxxx:/> fstyp -v /dev/vgHITACHI_SI_6/lvHIP16
vxfs
version: 4
f_bsize: 8192
f_frsize: 4096
f_blocks: 8187904
f_bfree: 122831
f_bavail: 121168
f_files: 26640
f_ffree: 30704
f_favail: 30704
f_fsid: 1078067201
f_basetype: vxfs
f_namemax: 254
f_magic: a501fcf5
f_featurebits: 0
f_flag: 16
f_fsindex: 7
f_size: 8187904



root@xxxx:/> fstyp -v /dev/vgHITACHI_SI_6/lvHIP17
vxfs
version: 4
f_bsize: 8192
f_frsize: 4096
f_blocks: 8187904
f_bfree: 8186856
f_bavail: 8058937
f_files: 2046736
f_ffree: 2046704
f_favail: 2046704
f_fsid: 1078067202
f_basetype: vxfs
f_namemax: 254
f_magic: a501fcf5
f_featurebits: 0
f_flag: 16
f_fsindex: 7
f_size: 8187904


root@xxx:/> fstyp -v /dev/vgHITACHI_SI_6/lvHIP18
vxfs
version: 4
f_bsize: 8192
f_frsize: 4096
f_blocks: 8187904
f_bfree: 8186856
f_bavail: 8058937
f_files: 2046736
f_ffree: 2046704
f_favail: 2046704
f_fsid: 1078067203
f_basetype: vxfs
f_namemax: 254
f_magic: a501fcf5
f_featurebits: 0
f_flag: 16
f_fsindex: 7
f_size: 8187904

[Daniel_RP]

After disk copy:

root@dumbo:/opt/omni/lbin> fstyp -v /dev/vgHITACHI_SI_6/lvHIP18
unknown_fstyp (no matches)

root@dumbo:/opt/omni/lbin> fstyp -v /dev/vgHITACHI_SI_6/lvHIP17
unknown_fstyp (no matches)

To mount it, a newfs is needed.