[Bug 455024] Re: resize2fs: memory allocation failed while trying to resize
Niklas Busch
niklas at buschland.se
Sat Oct 19 23:28:09 UTC 2013
I ran into the same problem on my ARM 5 machine with 512 MB RAM (Debian squeeze).
It has a LVM system consisting of 4*3 TiB disks.
I needed to shrink an EXT4 file system from 8.5 TiB to something like 7
TiB, and kept getting the "Memory allocation failed" error. So, I tried
to reduce it in smaller and smaller increments, but to no avail.
The basic system with the LVM off-line has a swap partition just under 1 GiB (1023.4 MiB according to gdisk).
While resize2fs was running, I was monitoring the mem/swap usage in a separate terminal (using free).
It never got close to filling the swap, but I thought "what the h*ll" and attached another disk with a huge SWAP partition, did swapon, and tried again. Now it worked. Again I monitored with free: It never used more than 1217 MiB of the SWAP.
Perhaps a test of requirements should be implemented (or at least a switch for it)? That way I wouldn't have to run e2fsck after each failed attempt.
Regarding the comment about most common configurations: perhaps you should rethink. I understand that you would not want to introduce something that would have bad consequences for enterprise configurations, but things are changing.
I could have moved all disks to my desktop machine with 16 GiB RAM and done it there, but it would have meant taking hardware apart. The reason the disks are attached to the little ARM box is that I want that storage on-line 24/7 and still be able to sleep at night (no fans).
I think this kind of set-up is becoming more common.
Just my 2 cents...
--
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
More information about the foundations-bugs
mailing list