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

[elatllat]

Thanks for the quick answer tytso.

I used resize2fs to do an online grow of from 8TB to 12TB and that worked fine.
now I'm trying to offline shrink it back down to 8TB and it's unable to do so.

I am using a raspberrypi so it's 32-bit and limited to 256MB and I have 2x that in swap.
I am using debian not ubuntu but I'm guessing this is common code.

uname -a
Linux test 3.6.11+ #474 PREEMPT Thu Jun 13 17:14:42 BST 2013 armv6l GNU/Linux

(taken during a "e2fsck -fy ")
free
             total       used       free     shared    buffers     cached
Mem:        237648     225440      12208          0      63240      11796
-/+ buffers/cache:     150404      87244
Swap:       475132      13444     461688

I was watching top and never saw it use more that 53% of the RAM but I
may have missed the crucial moment.

I'll contact linux-ext4 at vger.kernel.org as you suggest.

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