One final note, before I mute this bug. I don't consider it a bug that you can't shrink a file system with terabytes of disk space when you only have 256 or 512MB of memory. More to the point, I'm not paid to make e2fsprogs work well on that configuration. No other file system supports shirnking at all, and I doubt most file systems will able to handle this configuration well if they need to repair a badly corrupted file system when you only have this little memory (unless you enable swap and be prepared to wait for a long time).
If someone wants to try to make e2fsprogs work well for something that *I* consider to be an edge case (and yes, I have a bookshelf NAS box; it has Gigabytes worth of memory; funny, that), patches will be gratefully accepted. Send them to the linux-ext4 mailing list. Be warned, though, if it trashes performance on the vast majority of deployed use cases, I'm not going to accept the patch. While I agree that Ubuntu should upgrade to 1.42.9, as it fixes a very large number of bugs, including some that could cause data corruption, it's not going to handle this particular feature request. P.S. My cell phone has more memory that what some of the people on this list are proposing to use for a file server..... -- 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
