FS is larger than device(fsck needs checking)

[Akif_1]

Hi All,

Recently i upgraded the vg with the help of vgmodify , The volume group and lvolx respectively working fine, But the problem started when server rebooted.

Unable to mount /dev/vgx1/lvolx.

Problem diagnostics details below:

*fsck /dev/vgx1/lvolx
*fsck -y /dev/vgx1/lvolx


vgdisplay -v vgx1
--- Volume groups ---
VG Name /dev/vgx1
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 9
Open LV 9
Max PV 16
Cur PV 10
Act PV 6
Max PE per PV 11199
VGDA 12
PE Size (Mbytes) 32
Total PE 18553
Alloc PE 18553
Free PE 0
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

LV Name /dev/vgx1/lvolx
LV Status available/syncd
LV Size (Mbytes) 102400
Current LE 3200
Allocated PE 3200
Used PV 4

root@ruxtstdb > fstyp -v /dev/vgx1/lvolx
vxfs
version: 4
f_bsize: 8192
f_frsize: 4096
f_blocks: 26214400
f_bfree: 7456384
f_bavail: 7456384
f_files: 32
f_ffree: 2013201248
f_favail: 2013201248
f_fsid: 1073807365
f_basetype: vxfs
f_namemax: 254
f_magic: a501fcf5
f_featurebits: 0
f_flag: 16
f_fsindex: 7
f_size: 26214400
root@ruxtstdb >
root@ruxtstdb > bdf /dev/vgx1/lvolx
Filesystem kbytes used avail %used Mounted on
/dev/vgx1/lvolx 104857600 75032064 29825536 72%



Unable to mount the lvolx file system.
Need valuable input for the expert people.

Regard's

[Akif_1]

# /usr/sbin/fsck -F vxfs -o full,nolog -y /dev/vgx1/lvolx

file system is larger than device

vxfs fsck: cannot initialize aggregate

file system check failure, aborting ...

[Viktor Balogh]

> Unable to mount the lvolx file system.

and

> root@ruxtstdb > bdf /dev/vgx1/lvolx
> Filesystem kbytes used avail %used Mounted on
> /dev/vgx1/lvolx 104857600 75032064 29825536 72%

are paradox statements.

> Recently i upgraded the vg with the help of vgmodify ,

what did you mean by "upgraded"?

[Ismail Azad]

Hi Akif,

Same question... What upgradation?? Upgradation is normally done with vgversion... What exactly did you upgrade with vgmodify??

Regards
Ismail Azad

[Akif_1]

Hello,

A statment mistake "upgradation", But "vgmodify" purpose is to modify vg only to extend vg's to accommodate more space.

After increased vg size via vgmodify and lv's respectively increased , Everything goes fine untill reboot.

After reboot the system throws above errors.and i tried with fsck multiple options -y etc.

Regard's

[rariasn]

Hi:

Cur PV 10
Act PV 6 <---

Not all PV are active.

Rgs,