amazon attaches ebs vols to alternate device on HVM instances #34

Closed
jtriley opened this Issue Jul 20, 2011 · 5 comments

2 participants

@jtriley
Owner

starcluster attaches EBS volumes to /dev/sd* and expects the device to mountable via the /dev/sd* address. With HVM instances the EBS volume devices show up as /dev/xvd* instead. Need to also check for /dev/xvd* whenever /dev/sd* doesn't exist.

@jtriley jtriley was assigned Aug 1, 2011
@jtriley
Owner

actually this isn't true, I assumed this was the case just simply looking at a user's bug report on the mailing list:

http://mailman.mit.edu/pipermail/starcluster/2011-July/000752.html

Upon further investigation it turns out /dev/xvd* is a symlink to /dev/sd*. The issue experienced is most likely related to StarCluster checking whether /dev/sd* exists too quickly.

@jtriley
Owner

@srooks10 looks like you were using your new Ubuntu 11.04 HVM-AMI built from your new wiki guide (btw, thanks for contributing your guide!).

After looking a little deeper I found this on the ec2ubuntu google group:

http://groups.google.com/group/ec2ubuntu/browse_thread/thread/f10205927e884c58/f1d007503bdf9ecd

This seems to imply that /dev/xvd* is now the standard device name for EBS and /dev/sd* is no longer supported on Ubuntu 11.04. Now that I know this is the case it should be easy to add a patch for this that supports both the old /dev/sd* names and the new /dev/xvd* names.

I'll let you know when there's a patch ready for testing.

@jtriley jtriley closed this in 42076ee Aug 1, 2011
@jtriley
Owner

@srooks10 this should be fixed, however, would you mind checking out the latest code (in the "develop" branch) and testing whether it works with your custom 11.04 HVM AMI and an EBS volume?

@srooks10
@jtriley
Owner

@srooks10 great! glad it's working for you and thanks for testing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment