Yep, confirmed; normally users don't specify a size explicitly, and
simply allow resize2fs to use the size of the block device as the size
to use for the new file system --- and we have the appropriate tests in
that code path.
But if the user specifies the size explicitly, we aren't checking to
make sure the new size is too large. That's a bug, although most users
(hopefully) won't try to explicitly set a new file system size, which is
why no one has noticed up until now. So I wouldn't give this a very
high level of importance from a distro perspective, but it's something
that I will get fixed in the next release.
** Changed in: e2fsprogs (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/956038
Title:
resize2fs allows resize beyond maximum fs size - corrupts fs
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/956038/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
