Hey Jamie,
Why does all filesystem options default to ext2, and provide no option for using ext3 or ext4? Given how much more likely it is for a VM to have the plug pulled on it (figuratively speaking), it seems obvious we'd want journalling filesystems running on them whenever possible. It is, of course, possible to mount ext3 and ext4 via loop, so there's no technical reason I can think of not to allow, and even recommend, those filesystems.
Status:
Closed (fixed)
Comments
Submitted by andreychek on Thu, 07/07/2011 - 14:51 Comment #1
In case anybody was counting -- I did some poking around, and Ubuntu 10.04 and RHEL6 are using Ext4 for their default filesystem.
Debian 6 (along with all the older distros) use Ext3 for their default filesystem.
Submitted by JamieCameron on Thu, 07/07/2011 - 17:18 Comment #2
This is due to parted not supporting ext2 filesystems - at least on my test machine. However, using parted to create filesystems is a bad solution, so I will change Cloudmin to use mkfs in the next release.
Submitted by Issues on Thu, 07/21/2011 - 17:23 Comment #3
Automatically closed -- issue fixed for 2 weeks with no activity.