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

[elatllat]

An inode is only 256 bytes, the super block is only 1024 bytes, and I am
likely missing something here but I see no reason to require more than a
few inodes in RAM at any given time (and this seems to be the case for
creating, growing, checking, and repairing). I would expect resize2fs to
have a buffer of up to available RAM to speed things up, but only need a
few MB in RAM for any operation. I would also expect that If there was
some minimum amount of RAM required resize2fs would check and calculate
before hand and tell the user how much RAM is required. maybe even warn
when growing to a size  resize2fs will not be able to shrink down from.

I guess e2fsprogs still has some room to improve.

-- 
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