ext4 mount fails with "resize inode not valid" after a reboot

Ralf Hildebrandt Ralf.Hildebrandt at charite.de
Sun Apr 26 11:10:44 UTC 2009


With kernel 2.6.30-rc2-git6 and prior I am having problems mounting
ext4 partitions after reboot.

A successful mount looks like this:

/dev/cciss/c0d0p8 on /squid-cache0 type ext4 (rw,noexec,nodev,noatime,data=writeback,errors=panic)
/dev/cciss/c0d0p9 on /squid-cache1 type ext4 (rw,noexec,nodev,noatime,data=writeback,errors=panic)
/dev/cciss/c0d0p10 on /squid-data type ext4 (rw,noexec,nodev,noatime,data=writeback,errors=panic)

Dmesg reports:
[  242.297469] EXT4-fs: barriers enabled
[  242.302098] kjournald2 starting: pid 2509, dev cciss!c0d0p8:8, commit interval 5 seconds
[  242.311272] EXT4 FS on cciss!c0d0p8, internal journal on cciss!c0d0p8:8
[  242.311331] EXT4-fs: delayed allocation enabled
[  242.311386] EXT4-fs: file extents enabled
[  242.311562] EXT4-fs: mballoc enabled
[  242.311627] EXT4-fs: mounted filesystem cciss!c0d0p8 with writeback data mode
[  242.329741] EXT4-fs: barriers enabled
[  242.337949] kjournald2 starting: pid 2510, dev cciss!c0d0p9:8, commit interval 5 seconds
[  242.343248] EXT4 FS on cciss!c0d0p9, internal journal on cciss!c0d0p9:8
[  242.343317] EXT4-fs: delayed allocation enabled
[  242.343383] EXT4-fs: file extents enabled
[  242.343588] EXT4-fs: mballoc enabled
[  242.343662] EXT4-fs: mounted filesystem cciss!c0d0p9 with writeback data mode
[  242.366470] EXT4-fs: barriers enabled
[  242.371982] kjournald2 starting: pid 2511, dev cciss!c0d0p10:8, commit interval 5 seconds
[  242.379278] EXT4 FS on cciss!c0d0p10, internal journal on cciss!c0d0p10:8
[  242.379345] EXT4-fs: delayed allocation enabled
[  242.379410] EXT4-fs: file extents enabled
[  242.379594] EXT4-fs: mballoc enabled
[  242.379662] EXT4-fs: mounted filesystem cciss!c0d0p10 with writeback data mode

During boot I get these errors (Resize inod not valid):
http://www.arschkrebs.de/images/ext4-1.png
and the manual fsck reports:
http://www.arschkrebs.de/images/ext4-2.png

WTF is going on? This hapens even when I just recreate the filesystem.

-- 
Ralf Hildebrandt
  Geschäftsbereich IT | Abteilung Netzwerk
  Charité - Universitätsmedizin Berlin
  Campus Benjamin Franklin
  Hindenburgdamm 30 | D-12200 Berlin
  Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962
  Ralf.Hildebrandt at charite.de | http://www.charite.de




More information about the Ext3-users mailing list