© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
Yes, sorry, there are two different problems here. The one I was talking about happens when you go above 16TB. That fix is easy.
Going to a fs size a little greater than 1TB is triggering another problem from a file system originally created with 1G file size, which I've replicated and I've confirmed that it's taking place on 1.42.x as well as e2fspros 1.41.x. The problem is that when we run out of reserved GDT blocks, resize2fs isn't noticing and ends up corrupting the file system.
The workaround for now is to explicitly create the file system with an expected maximum resize: mke2fs -t ext4 -E resize=8T /dev/tiny
You'll need to do this if you want to resize to succeed in any case. I agree resize2fs should notice this case and deal with it more intelligently.