<div dir="ltr">Nevermind. I see this is actually 'DEVICE' in cluster.py except it only likes /dev/sd*. I think this should be changed to allow /dev/xvda*. In CentOS 6, /dev/sd* gets renamed. I've discovered if I specify an EBS volume device path to /dev/xvd*, it holds. <br></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Apr 4, 2015 at 2:02 PM, Ryan G <span dir="ltr"><<a href="mailto:ngsbioinformatics@gmail.com" target="_blank">ngsbioinformatics@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div><div>I'm playing around with using StarCluster and different AMIs. One of the things I've noticed is that EBS volumes don't get mounted where expected. For instance, my config file specifies something like:<br><br>[volume biodata]<br># attach vol-c9999999 to /home on master node and NFS-shre to worker nodes<br>VOLUME_ID = vol-c999999<br>MOUNT_PATH = /home<br><br></div>StarCluster then tries to attach the volume at /dev/sdz, But ends up giving the error "Cannot find device /dev/xvdz". When I log in, I see the volume got attached to /dev/xvdaz. <br><br></div>I can either modified my copy of StarCluster to correct for this, but I think a better solution would be to be able to specified the block device:<br><br>[volume biodata]<br># attach vol-c9999999 to /home on master node and NFS-shre to worker nodes<br>VOLUME_ID = vol-c999999<br>MOUNT_PATH = /home<br></div>BLOCK_DEVICE = /dev/xvdaz<br><br></div>This way, the user can control where the mount is happening and expected.<br><br></div>Thoughts?<br></div>
</blockquote></div><br></div>