"tune2fs -I 256" extremly slow

[Andreas Schultz]

Binary package hint: e2fsprogs

gave up on a inode resize after some hours

from http://marc.info/?l=linux-ext4&m=122672822822037&w=2

    tune2fs: Fix inefficient O(n**2) algorithms when expanding the inode size

    When running "tune2fs -I 256" on moderate to large filesystems, the
    time required to run tune2fs can take many hours (20+ before some
    users gave up in disgust). This was due to some O(n**2) and O(n*m)
    algorithms in move_block() and inode_scan_and_fix(), respectively.

[Andreas Schultz (aschultz)]

gentoo believes they have fixed this bug, but they have not.

The patch from http://marc.info/?l=linux-ext4&m=122795607322413&w=2 (or something along that lines) is required on top of upstream git to get decent performance.

[Craig (candrews-integralblue)]

Perhaps you should tell Gentoo that? I doubt they monitor this bug ;-)

[Theodore Ts'o (tytso)]

This will be fixed in e2fsprogs 1.41.4. The changes have been checked in, but a number of other high priority bugs needs to be fixed before I release...

[Julien Plissonneau Duquene (julien-plissonneau-duquene)]

Fix released in 1.41.4-1ubuntu1.