)]}'
{"doc/source/user_guide/building_an_image.rst":[{"author":{"_account_id":6488,"name":"Clint Byrum","email":"clint@fewbar.com","username":"clint-fewbar"},"change_message_id":"b246569c1212c925826895420b7865b81a88c32e","unresolved":false,"context_lines":[{"line_number":58,"context_line":"Filesystem Caveat"},{"line_number":59,"context_line":"-----------------"},{"line_number":60,"context_line":""},{"line_number":61,"context_line":"By default, disk-image-create uses a 4k byte-to-inode ratio when creating the filesystem in the image. This provides large \u0027whole-system\u0027 images to utilize several TB disks without exhausting inodes. In contrast, when creating images intended for tenant instances, this ratio consumes more disk space than an end-user would expect (e.g. a 50GB root disk has 47GB avail.). If the image is intended to run within a tens to hundrededs of gigabyte disk, setting the byte-to-inode ratio to the ext4 default of 16k will allow for more usable space on the instance. The default can be overridden as:"},{"line_number":62,"context_line":""},{"line_number":63,"context_line":"::"},{"line_number":64,"context_line":"    disk-image-create --mkfs-options \u0027-i 16384\u0027 \u003cdistro\u003e vm"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a710552_880c7995","line":61,"updated":"2015-12-16 00:47:43.000000000","message":"Please wrap this at 72 chars. Also \n\ns/This provides large/This allows large/\n\nAnd\n\ns/The default can be overridden as/The default can be overridden by passing --mkfs-options like this::/\n\nNote that there\u0027s no need for the extra lone :: at the end of this paragraph, just end the one with the double colon to start the literal.","commit_id":"c2b10bb31e17c70ef47b8ae70d39295e712f239d"}]}
