No problem; this should get you there: 1. With CloudMan running, go to the Admin console and stop Galaxy and PostgreSQL services (in that order) 2. From instance's CLI: sudo umount /mnt/galaxyTools 3. From the AWS console, detach the tools volume (but remember as which device it was attached) 4. From the AWS console, create a snapshot of the detached volume 5. From the AWS console, create a new volume from the newly created snapshot of the desired size. 6. From the AWS console, attach the new larger volume to the running instance (attach it as a different device then the original volume that was attached) 7. From instance's CLI: sudo mount <device> /mnt/galaxyTools 8. From instance's CLI: sudo xfs_growfs /mnt/galaxyTools 9. From instance's CLI: sudo umount /mnt/galaxyTools 10. From the AWS console, detach the volume and create a snapshot 11. From the AWS console, attach the original volume as the same device as it was attached 12. From instance's CLI: sudo mount <device> /mnt/galaxyTools 13. From CloudMan Admin, 'File systems' service should be running now. If so, start PostgresSQL and Galaxy services (in that order) 14. From CloudMan, Terminate cluster 15. From the AWS S3 console, in the cluster's bucket, edit the 'persistent_data.yaml' galaxyTools file system to point to the new snapshot and its size is properly set (snapshot from step 10) 16. Start the cluster back up using the same user data. Now you should have the new file system there and any changes you want to make can be done from CLI. Then persist file system changes from the CloudMan Admin to keep those around after you restart the cluster. I have not actually tried this but am speaking from memory so there may be things that do not end up working quite like this but the general concept is there. Good luck and let us know how it goes. Enis On Fri, Feb 17, 2012 at 12:34 AM, Dave Lin <dave@verdematics.com> wrote:

Hi Enis,

I installed a new test cluster earlier today and did notice that the new clusters magically now have galaxyTool volumes with 10GB. That is a good change.

However, you are correct. I have an existing cluster (that had the old 2 GB volume size) that I'm trying to expand. With additional tools and log files, that volume keeps getting full.

Can you help guide me through this process?

Thanks again, Dave On Thu, Feb 16, 2012 at 2:36 PM, Enis Afgan <eafgan@emory.edu> wrote:

...

Hi Dave, Are you trying to modify the size of the tools volume for a cluster that's been around for a while and you customized already or could this be a new cluster? The reason I'm asking is because as of Tuesday (3 days ago), the default tools volume for any new cluster will be 10GB (vs 2GB previously) and only 1.7GB are taken. I would hope that gives plenty of storage space for majority of anyone's needs.

Let me know if you need to modify an existing cluster and I'll guide you through the process then.

Enis

On Thu, Feb 16, 2012 at 9:31 PM, Dave Lin <dave@verdematics.com> wrote:

...

Hi All,

What is the recommend process for expanding the galaxyTool volume for an existing galaxy instance (using EC2/cloudman)?

I tried the following, but it didnt' work for me.

0) Terminate cluster.

1) Amazon EC2- create snapshot of current galaxyTools volume 2) Amazon EC2- create volume from step 1 + specify desired volume size. 3) Amazon EC2- create new snapshot from Step 2. 4) Amazon S3- identify S3 bucket for this cluster. Modify persistent_data.yaml. Modify size and snap_id to correspond with step #3 5) Amazon EC2- Start new instance-- using same AmazonID + ClusterName

I was expecting the new instance to startup and create a galaxyTools volume based on the snapshot identified in the persistent_data.yaml file, but that didn't seem work.

Thanks in advance for any pointers. Dave

___________________________________________________________ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at:

http://lists.bx.psu.edu/