ext4 mount fails with "resize inode not valid" after a reboot
Ralf.Hildebrandt at charite.de
Sun Apr 26 14:15:18 UTC 2009
* Eric Sandeen <sandeen at redhat.com>:
> Ralf Hildebrandt wrote:
> > With kernel 2.6.30-rc2-git6 and prior I am having problems mounting
> > ext4 partitions after reboot.
> > WTF is going on? This hapens even when I just recreate the filesystem.
> So mkfs followed immediately by fsck shows it, or only with a mount in
> between? Does e2fsprogs-1.41.5 (released about 2 days ago) still show
> the problem? If so can you mkfs & provide the dumpe2fs -h output right
> after the mkfs, perhaps there is something unique about your fs geometry
> that trips a bug.
Right now I updated e2fsprogs-1.41.5 to and rebooted all my 4 machines
and the error did not occur. I'll have to report back.
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