Comment 7 for bug 1427160

I've provisioned a brand new compute node on the cluster I'm working on, and it came up with similiar partitioning, note that we have not done any customer partitioning in MAAS:

ubuntu@compute09:~$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda1 9.1G 1.3G 7.4G 15% /
none 4.0K 0 4.0K 0% /sys/fs/cgroup
udev 378G 4.0K 378G 1% /dev
tmpfs 76G 996K 76G 1% /run
none 5.0M 0 5.0M 0% /run/lock
none 378G 0 378G 0% /run/shm
none 100M 0 100M 0% /run/user
/dev/sda6 80G 56M 75G 1% /home
ubuntu@compute09:~$ free -g
             total used free shared buffers cached
Mem: 755 5 750 0 0 0
-/+ buffers/cache: 4 750
Swap: 3 0 3
ubuntu@compute09:~$ sudo fdisk -l

Disk /dev/sda: 100.0 GB, 99994337280 bytes
255 heads, 63 sectors/track, 12156 cylinders, total 195301440 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 262144 bytes / 262144 bytes
Disk identifier: 0x0009f6a0

   Device Boot Start End Blocks Id System
/dev/sda1 * 512 19531263 9765376 83 Linux
/dev/sda2 19531774 195300863 87884545 5 Extended
Partition 2 does not start on physical sector boundary.
/dev/sda5 19531776 26638847 3553536 82 Linux swap / Solaris
/dev/sda6 26639360 195300863 84330752 83 Linux