© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
As I mentioned above this issue seemed to occur intermittently if you build and deploy new images all the time. It is however reproducible once you hit it if you use the same DIB image again and again. Once you have an image that fails it seems that it will continue to fail... Aha!
Jon recently reported the issue on the ext4 list here and Ted's reply shed some light on the root cause here:
http://
We were able to trace it back to this DIB commit:
https:/
The short story is there *is* an ext4 resize bug that needs fixing. However we can almost certainly avoid the issue entirely by using ext4 defaults here which should be reasonable for most cases. The default allows for a root partition up to 4TB (I think).
Anyway, The root cause of all this is really a design problem in DIB/TripleO at the moment in that we shouldn't have to worry about the max size of the root file system when creating our images. Ideally we'd just mkfs on the root file system itself. Much more efficient, and avoids this problem altogether...
I think the best thing to do today to avoid this is make setting max-online-resize an option in DIB. This will allow us to stick to the (well tested) ext4 defaults for most cases, and if someone has need for a large root filesystem they can easily bump the setting. This may be temporary until we either fix the design... or the ext4 fix is released.