fsck error: "file system is larger than device"

[Daniel_RP]

fsck: /etc/default/fs is used for determining the file system type
file system is larger than device
vxfs fsck: cannot initialize aggregate
file system check failure, aborting ...


How Can we solve this problem?

[Peter Godron]

Carlos,
depends on what were you trying to do.
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=603597
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=991283


Also:
http://forums1.itrc.hp.com/service/forums/helptips.do?#33

[Yang Qin_1]

Hi, can you check the vg involved and see if there is a disk missing?

vgdisplay -v vg##

fsck command was executed during the system startup or you run it manually?


Yang

[Daniel_RP]

Hi all,

I attach some information about it:

lvdisplay /dev/vgHITACHI_P6/lvHIP16
--- Logical volumes ---
LV Name /dev/vgHITACHI_P6/lvHIP16
VG Name /dev/vgHITACHI_P6
LV Permission read/write
LV Status available/syncd
Mirror copies 0
Consistency Recovery MWC
Schedule striped
LV Size (Mbytes) 31984
Current LE 7996
Allocated PE 7996
Stripes 4
Stripe Size (Kbytes) 128
Bad block on
Allocation strict
IO Timeout (Seconds) default




fstyp -v /dev/vgHITACHI_P6/lvHIP16
vxfs
version: 4
f_bsize: 8192
f_frsize: 4096
f_blocks: 8192000
f_bfree: 8190952
f_bavail: 8062969
f_files: 2047760
f_ffree: 2047728
f_favail: 2047728
f_fsid: 1074266113
f_basetype: vxfs
f_namemax: 254
f_magic: a501fcf5
f_featurebits: 0
f_flag: 16
f_fsindex: 7
f_size: 8192000



vgdisplay /dev/vgHITACHI_P6
--- Volume groups ---
VG Name /dev/vgHITACHI_P6
VG Write Access read/write
VG Status available, exclusive
Max LV 255
Cur LV 3
Open LV 3
Max PV 16
Cur PV 4
Act PV 4
Max PE per PV 5999
VGDA 8
PE Size (Mbytes) 4
Total PE 23996
Alloc PE 23988
Free PE 8
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

Thanks in advance.

[siva0123]

Hi,
1.Check dmesg , Syslog , /var/opt/resmon/log/event.log and teh cstm o/p for any hardware issues. also check whether all teh disks are claimed.

2. run bdf and check whether all the filsystems are showing it's actual size.

3. run lvdisplay and check whether the size of that lv and the filesystem size are same, i 've noted in some rare cases this is not the case.

If that is all fine , try the fsck command with an alternate superblock copy which will be available in /etc/sbtab

Thanks,
Siva

[siva0123 · Accepted solution]

carlos ,

What is the bdf showing abt the filsystem size , my assupmtion is it should be different than the lvsize shown in lvdisplay
Show me the bdf o/p for this lv

Siva

[siva0123]

My calculation from the fstype output shows the filesystem size is approximately 64 GB and the lvdisplay shows the lvsize is approximately 32 GB

Is that correct ?

[siva0123]

Carlos,

If that is the case then yo have the follwoing options,
1. Reduce the filesystem size using online jfs

Or
2. Increase the LV size

or

3. Recreate the filesystem and restore using backup.

[Daniel_RP]

Hi, Yang Qin.

I run it manually.

vgdisplay -v vgHITACHI_P6
--- Volume groups ---
VG Name /dev/vgHITACHI_P6
VG Write Access read/write
VG Status available, exclusive
Max LV 255
Cur LV 3
Open LV 3
Max PV 16
Cur PV 4
Act PV 4
Max PE per PV 5999
VGDA 8
PE Size (Mbytes) 4
Total PE 23996
Alloc PE 23988
Free PE 8
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

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

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

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


--- Physical volumes ---
PV Name /dev/dsk/ch22t2d1
PV Status available
Total PE 5999
Free PE 2
Autoswitch On

PV Name /dev/dsk/ch22t2d3
PV Status available
Total PE 5999
Free PE 2
Autoswitch On

PV Name /dev/dsk/ch22t2d5
PV Status available
Total PE 5999
Free PE 2
Autoswitch On

PV Name /dev/dsk/ch22t2d7
PV Status available
Total PE 5999
Free PE 2
Autoswitch On

Thanks.

[Yang Qin_1]

Hi, Carlos, Can you post the output from bdf /dev/vgHITACHI_P6/lvHIP16?

Please let us know by doing what you received this error, (extend the file system?) it will help us to understand the problem.

Yang

[Daniel_RP]

Hi Sivagnanaselvan ,

I can't check lvsize with bdf because I can't mount this lv.

This filesystem is new, it's empty. There was no information in it.


Thanks.

[Daniel_RP]

Sorry, I was confused.
You're right:

bdf /dev/vgHITACHI_P6/lvHIP16

Filesystem kbytes used avail %used Mounted on
/dev/vgHITACHI_P6/lvHIP16
32768000 4192 32251876 0%



Thanks.

[siva0123]

Carlos ,

From the fstype o/p i 've calculated your filesystem size

It can be calculated as ((f_bsize*f_size)/1024/1024)

For your case it is ((8192*81920000)/1024/1024) =64000MB

But the vgdisplay -v command reports that your lvsize is 319XX MB ,

So definitely there is a mismatch in your filsystem size and the corresponding lv size.

Try to reduce your filesystem size to 32 GB or increas ethe size of your LV to 64GB


Thanks,
Siva

[Yang Qin_1]

From which command you received this error?
Did you run "newfs -F vxfs /dev/vgHITACHI_P6/rlvHIP16"? after you create lvol with lvcreate?


Yang

[siva0123]

Carol,

I'm not completely right .

Your bdf o/p shows the filsystem size as 32000 MB and the VG display shows your LVsize as 31984MB.

That means you have created a filesystem which is larger than your Logical Volume.


If you say the filesystem is empty why cant you try to recreate the filesystem from the scratch which will be equal to your Logical volume.


Thanks,
Siva

[Daniel_RP]

fs size & lv size would have to be 31984 Mbytes.

It's not possible to increase lv size to 64 GB.

I will investigate how to reduce file system size to 31984 MB.

Thanks a lot.

I will close this post if I will finish correcly the operation.

[Daniel_RP]

I run:
# newfs -F vxfs /dev/vgHITACHI_P6/rlvHIP16

version 4 layout
32751616 sectors, 8187904 blocks of size 4096, log size 512 blocks
unlimited inodes, largefiles not supported
8187904 data blocks, 8186800 free data blocks
250 allocation units of 32768 blocks, 32768 data blocks
last allocation unit has 28672 data blocks



And then I tried to fsck lvHIP16:

fsck /dev/vgHITACHI_P6/rlvHIP16

fsck: /etc/default/fs is used for determining the file system type
file system is clean - log replay is not required


fsck is ok!!!


But now I get:"vxfs mount: mount option(s) incompatible with file system /dev/vgHITACHI_P6/lvHIP16"

When trying to mount it: "/usr/sbin/mount -F vxfs -o rw,suid,delaylog,largefiles,datainlog /dev/vgHITACHI_P6/lvHIP16 /p16"

[Daniel_RP]

Sorry, firstly:

I have ran newfs command without "-o largefiles" parameter.

How Can I change it?

[Daniel_RP]

Sorry, firstly:

I have ran newfs command without "-o largefiles" parameter.

Anybody knows how can I change it?

[siva0123]

Carlos,

If i'm not wrong i see the filesystem was created with no large file support but you are trying to mount the filesystem with large file support .


Try mounting it without the large files option.


Thanks,
Siva

[siva0123]

If you dont have any data on the filesystem ,
i think you can try the newfs comand again with -o option specified and then try to mount it.

Gud luck.

Thanks,
Siva

[Yang Qin_1]

you need to add "largefiles" option to your lvol if you use largefiles as an option to mount it.

try: fsadm -F vxfs -o /dev/vgHITACHI_P6/lvHI


if you have problem, do a "lvremove /dev/vgHITACHI_P6/lvHI" then recreate it with lvcreate. "newfs -F vxfs -o largefiles /dev/vgHITACHI_P6/rlvHI"


Yang

[Yang Qin_1]

sorry should be "fsadm -F vxfs -o largefiles /dev/vgHITACHI_P6/lvHI"

Yang

[Daniel_RP]

lvremove --> ok
lvcreate --> ok

On execute newly "newfs -F vxfs ...":

I get:

"vxfs newfs: /dev/vgHITACHI_P6/lvHIP16 is not a character device"

Any idea?

[Vasu Viswanadha]

Use

/dev/vgHITACHI_P6/rlvHIP16