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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/455024 Title: resize2fs: memory allocation failed while trying to resize To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/455024/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
