I see how that would work for volumes inside of /mnt as per the example in rubber.yml, but I'm trying to do this with /mnt itself:
roles:
 my_role:
  availability_zone: us-west-1b
  volumes:
   - size: 100 # size of vol in GBs
    zone: us-west-1b # zone to create volume in, needs to match host's zone
    device: /dev/sdh # OS device to attach volume to
    mount: /mnt # The directory to mount this volume to
    mount_opts: defaults
    filesystem: ext4 # the filesystem to create on volume  Â
ubuntu@staging-encode2:~$ df -h
Filesystem    Size  Used Avail Use% Mounted on
/dev/xvda1 Â Â Â 7.9G Â 1.9G Â 5.7G Â 25% /
udev       3.4G  8.0K  3.4G  1% /dev
tmpfs      1.4G  172K  1.4G  1% /run
none       5.0M   0  5.0M  0% /run/lock
none       3.4G   0  3.4G  0% /run/shm
/dev/xvdb    414G  199M  393G  1% /mnt
As you can see, /mnt mounts to /dev/xvdb making it unavailable for /tmp. Â
If I change /mnt in rubber.yml above to /tmp, I get this in my instance. Â You can see that /mnt is auto-mounted by Rubber:
ubuntu@staging-encode2:~$ df -h
Filesystem    Size  Used Avail Use% Mounted on
/dev/xvda1 Â Â Â 7.9G Â 1.9G Â 5.7G Â 25% /
udev       3.4G  8.0K  3.4G  1% /dev
tmpfs      1.4G  172K  1.4G  1% /run
none       5.0M   0  5.0M  0% /run/lock
none       3.4G   0  3.4G  0% /run/shm
/dev/xvdb    414G  199M  393G  1% /mnt
/dev/xvdh     99G  188M  94G  1% /tmp