Comment 11 for bug 432620

# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# / was on /dev/sda4 during installation
UUID=67904705-b186-4d51-96e3-0dae4399346c / ext4 errors=remount-ro 0 1
# /boot was on /dev/sda2 during installation
UUID=ba9c30de-9d4e-4ff1-b50a-2b3c3c23ad2b /boot ext2 defaults 0 2
# /home was on /dev/mapper/wolfdale-home during installation
UUID=a5b5d14f-e2c2-49a4-b1d4-05b0309534e8 /home ext4 defaults 0 2
# swap was on /dev/sda6 during installation
UUID=9a1989f9-c0e2-4746-ba08-b0869d9d209a none swap sw 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0
# /home/anubis/backup was on /dev/mapper/wolfdale-backup during installation
UUID=ba830f6e-f634-42fd-9fb3-61a9d5ca6d15 /home/anubis/backup ext4 defaults 0 2
# /home/anubis/mythrec was on /dev/mapper/wolfdale-mythtv during installation
UUID=90ede06f-40f4-40bf-9cb1-8e623e00ce4d /home/anubis/mythrec xfs defaults 0 2
# /home/anubis/storage was on /dev/mapper/wolfdale-storage during installation
UUID=e09b01df-35dd-4f86-b870-1c59dc6c2266 /home/anubis/storage xfs defaults 0 2
# /home/anubis/terabyte was on /dev/mapper/wolfdale-terabyte during installation
UUID=9d865078-8835-4d2d-9601-34b75b3c393f /home/anubis/terabyte xfs defaults 0 2

Confirmed same here with my XFS partitions. Mythrec and Storage do not automount, but Terabyte does. Weird?
http://ubuntuforums.org/showthread.php?p=8039064