Changing block size prevents new instances from booting

Craig Menning's Avatar

Craig Menning

19 Dec, 2014 05:19 PM


In, y'all suggested tweaking the /etc/mke2fs.conf file to adjust the number of inodes on our web servers.

When I update the default blocksize to 1024 (from 4096, since we have a ton of tiny files) in mke2fs.conf and take a snapshot, however, the new image won't boot.

  1. Support Staff 1 Posted by Marat Komarov on 22 Dec, 2014 08:57 AM

    Marat Komarov's Avatar

    EC2 console output should give an error details, and an explanation why image can't boot. This should help you to debug this issue.

    As for my original suggestion - I haven't tested it. It was an idea how you could achieve your needs.


  2. Marat Komarov closed this discussion on 20 Jan, 2015 10:25 AM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts


? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac

Recent Discussions

02 Jul, 2019 07:54 PM
07 Jun, 2019 07:12 PM
02 May, 2019 04:04 PM
28 Mar, 2019 05:24 PM
22 Feb, 2019 08:11 PM