[openstack-dev] [nova] - Revert change of default ephemeral fs to ext4

Matt Riedemann mriedem at linux.vnet.ibm.com
Tue Dec 16 22:18:45 UTC 2014

On 12/30/2013 7:30 PM, Clint Byrum wrote:
> Excerpts from Day, Phil's message of 2013-12-30 11:05:17 -0800:
>> Hi, so it seems we were saying the same thing - new vms get a shared "blank" (empty) file system,  not blank disc.  How big a problem it is that in many cases this will be the already created ext3 disk and not ext4 depends I guess on how important consistency is to you (to me its pretty important).  Either way the change as it stands wont give all new vms an ext4 fs as intended,  so its flawed in that regard.
>> Like you I was thinking that we may have to move away from "default" being in the file name to fix this.
> Indeed, "default"'s meaning is mutable and thus it is flawed as a
> cache key.
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

jogo brought this bug up in IRC today [1]. The bug report says that we 
should put in the Icehouse release notes that ext3 is going to be 
changed to ext4 in Juno but that never happened.  So question is, now 
that we're well into Kilo, what can be done about this now?  The thread 
here talks about doing more than just changing the default value like in 
the original change [2], but is someone willing to work on that?

[1] https://bugs.launchpad.net/nova/+bug/1266262
[2] https://review.openstack.org/#/c/63209/



Matt Riedemann

More information about the OpenStack-dev mailing list