<div dir="ltr">sorry if you've received this message before. I just saw the following message was sent to the spam folder in my gmail account. So I figure I'd better resend it through my gmail account. Thanks and have a great holiday!<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Dec 23, 2014 at 12:05 PM, Jian Feng <span dir="ltr"><<a href="mailto:freedafeng@yahoo.com" target="_blank">freedafeng@yahoo.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div style="color:#000;background-color:#fff;font-family:HelveticaNeue,Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif;font-size:16px"><div dir="ltr">Hello there,</div><div dir="ltr"><br></div><div dir="ltr">We want to create a cluster where each node has a couple of tele-bytes disk space for its own. The space in a node is used to store large data sets that will be processed by this particular node. </div><div dir="ltr"><br></div><div dir="ltr">I understand that we can create EBS volumes and then starcluster can mount them as network shared disks. So from there, I can create a symbolic link for each node to use the network disks, sth like</div><div dir="ltr"><br></div><div dir="ltr">ln -s /data/volumn0001 /localdisk</div><div dir="ltr"><br></div><div dir="ltr">This should work, but I am wondering if there is a cleaner solution. Also, I need the space is accessible right after the cluster is up or rebooted, because some init.d jobs will try to read/write the data in the disks.</div><div dir="ltr"><br></div><div dir="ltr">Thanks!</div></div></div><br>_______________________________________________<br>
StarCluster mailing list<br>
<a href="mailto:StarCluster@mit.edu">StarCluster@mit.edu</a><br>
<a href="http://mailman.mit.edu/mailman/listinfo/starcluster">http://mailman.mit.edu/mailman/listinfo/starcluster</a><br>
<br></blockquote></div><br></div>