touch-packages team mailing list archive

[Church <455024@xxxxxxxxxxxxxxxxxx>]

Googled up few related threads with solve mentioned adding swap. Even
with 4G ram & 10G swap it didn't help me though for rather full 5.5T
ext4 fs with big number of files. It seems that i could somewhat
workaround it by specifying some middle fs size between one -M tried to
reduce to and that of fs original size by calculating with bc
#M_blocksize#*4/1024^2 and throwing few tenhs of gigs above that.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, 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