[Bug 455024] Re: resize2fs: memory allocation failed while trying to resize

[Theodore Ts'o]

Resize2fs needs to keep track of which blocks need to be relocated, and
which inode its associated with (so it can update the block reference
after we copy the block from the portion of the file system that is
going to be gone after we finish with the shrink operation).

I am sure that e2fsprogs still has room to improve.   However,  I'm not
going to accept patches which make things worse for the most common
configurations, which are typically (a) small amounts of memory, and
small amounts of storage (i.e., a Android device with 512MB to 4GB of
memory, and generally 8-32GB of flash; Linode or Amazon EC3 VM's will be
roughly the same, but they will have much slower emulated HDD's instead
of flash), or (b) an enterprise server with 8GB to 64GB with 4-12TB of
disks.   Patches which make things better for your configuration, but do
not make things worse for these much more common configuration (and
which don't break e2fsprogs's built in regression test suite) will be
gratefully accepted.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to e2fsprogs in Ubuntu.
https://bugs.launchpad.net/bugs/455024

Title:
  resize2fs: memory allocation failed while trying to resize

Status in “e2fsprogs” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: e2fsprogs

  When I try to resize a big EXT3 filesystem on a RAID5 (/dev/md0) from
  5TB to 7TB i get this output:

  # resize2fs -p /dev/md0                                 
  resize2fs 1.41.9 (22-Aug-2009)
  Resizing the filesystem on /dev/md0 to 1709329888 (4k) blocks.
  Start von Durchgang 1 (max = 14904)
  Vergrößere die Inode-TabelleXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
  resize2fs: Memory allocation failed beim Versuch, die Größe von /dev/md0 zu ändern
  Please run 'e2fsck -fy /dev/md0' to fix the filesystem
  after the aborted resize operation.

  Note: Im using Ubuntu Hardy due to its LTS. But I installed the
  packages from Karmic, because they had no special dependencies, I
  could install them without any problem. The message above is from this
  updated e2fsprogs version (note the version). I get the exactly same
  message from the original e2fsprogs, except the last two lines (Please
  run...).

  I use 4KB Blocks, so EXT3 should be able to address 8TB...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/455024/+subscriptions