FSCK check failure

[affin]

Dear Friends,

we have an 11.11 box.
Today trying to fsck a logical volume we get the following message:

fsck
file system is larger than device
vxfs fsck: cannot initialize aggregate
file system check failure, aborting ...

our volume is so composed:
--- Logical volumes ---
LV Name /dev/vgsvilbv/lvhome
VG Name /dev/vgsvilbv
LV Permission read/write
LV Status available/syncd
Mirror copies 0
Consistency Recovery MWC
Schedule parallel
LV Size (Mbytes) 8500
Current LE 2125
Allocated PE 2125
Stripes 0
Stripe Size (Kbytes) 0
Bad block on
Allocation strict
IO Timeout (Seconds) default


We tried to specify the FS type and the force option without success.
Any ideas?


Many Thanks,
Alessandro Potenziani

[Joseph Loo]

hi,

nothing like a little search among the threads to find this:

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

hope it help.

regards.

[affin]

Joseph,


the article doesn't help me.
In fact the LV is bigger than FS but the fsck error still appears.


need more suggestion.
Alessandro

[Robert-Jan Goossens]

Hi Alessandro,

Could you post

# fstyp -v /dev/vgsvilbv/lvhome

Robert-Jan

[affin]

Dear Robert-Jan,


below the fstyp -v command.
Thanks,
AP



# fstyp -v /dev/vgsvilbv/lvhome
vxfs
Cannot open /dev/vgsvilbv/lvhome: Invalid argument
Cannot open /dev/vgsvilbv/lvhome: Invalid argument

version: 4294967295
f_bsize: 8192
f_frsize: 1024
f_blocks: 8704000
f_bfree: 7578065
f_bavail: 7104436
f_files: 1939828
f_ffree: 1894516
f_favail: 1894516
f_fsid: 1074135043
f_basetype: vxfs
f_namemax: 254
f_magic: a501fcf5
f_featurebits: 0
f_flag: 16
f_fsindex: 7
f_size: 8704000

[Joseph Loo]

hi,

how about this:

http://www1.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000072760980

in your case:

# lvextend -L (more than 8500) /dev/vgsvilbv/lvhome
# extendfs /dev/vgsvilbv/rlvhome

regards.

[affin]

I can't access the document.
I already extended the LV (is now 9000MB) and tried to extend the FS gave the error message that it's dirty.

AP

[Joseph Loo]

oops, sorry, the next few steps after extendfs are:

Do a full file system check

# fsck -F vxfs -o full -y /dev/vgsvilbv/rlvhome

mount your filesystem.

# mount /dev/vgsvilbv/lvhome

regards.

[affin]

# fsck -F vxfs -o full -y /dev/vgsvilbv/rlvhome
file system is larger than device
vxfs fsck: cannot initialize aggregate
file system check failure, aborting ...


AP

[Joseph Loo]

the whole article read as this:

RESOLUTION
The error is due to trying to restore a filesystem to a device that is not
large enough to accomodate it. You can resolve the error with the following
steps:


Set the appropriate size that the filesystem needs to be (where size is
slightly larger by a few PE's.)

# lvextend -L size /dev/vgXX/lvolX
# extendfs /dev/vgXX/rlvolX

Do a full file system check

# fsck -F vxfs -o full -y /dev/vgXX/rlvolX

You can now mount your filesystem.

# mount /dev/vgXX/lvolXX /mount-pt

it seems u need more than 9000MB, but could u reply this output:

# lvdisplay /dev/vgsvilbv/lvhome

regards.

[affin]

Joseph,

unfortunately the suggestion did not work:

# lvextend -L 12000 /dev/vgsvilbv/lvhome
Logical volume "/dev/vgsvilbv/lvhome" has been successfully extended.
vgcfgbackup: /etc/lvmtab is out of date with the running kernel:Kernel indicates 4 disks for "/dev/vgsvilbv"; /etc/lvmtab has 3 disks.
Cannot proceed with backup.

# extendfs -F vxfs /dev/vgsvilbv/rlvhome
vxfs extendfs: FS is dirty, run fsck first.

# fsck -F vxfs -o full -y /dev/vgsvilbv/rlvhome
file system is larger than device
vxfs fsck: cannot initialize aggregate
file system check failure, aborting ...


Regards,
AP

[Joseph Loo]

hi,

u definitely got a more serious problem judging from the last error message.

r u able to access this doc:

http://www1.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000076088072

if indicate this ID, HPUXKBRC00015714, in the technical knowledge base.

anyway, how did this happen?

regards.

[affin]

Joseph,


i can't access that document too...
This sad situation come from a reboot coomand issued yesterday.
I don't know why the kernel shows 4 disks. This LV is formed by 2 disks from the beginning and it never had a PV extesion.


AP

[Joseph Loo]

quite a lengthy doc.

by the way, which version is the HPUX?

regards.

[affin]

I still don't understand.
Why the kernel indicates a different number of PV if this VG had never and never a modify??
The version of OS is 11.11.


Thanks,
AP

[Kent Ostby]

I suspect that the root cause of this problem probably lies in this:

vgcfgbackup: /etc/lvmtab is out of date with the running kernel:Kernel indicates 4 disks for "/dev/vgsvilbv"; /etc/lvmtab has 3 disks.
Cannot proceed with backup.

The number of disks that the system thinks are in this VG is different then what you think and is inconsisten.

Please post output from "strings /etc/lvmtab" and vgdisplay -v /dev/vgsvilbv .

Best regards,

Oz