I am brand new to Galaxy and am currently having trouble uploading files to Cloudman via FTP. Specifically, I have been trying to upload several .bam files since last night using Filezilla, In the 16+ hour period, one of the .bam files uploaded successfully and I can access it in cloudman. The others have been continually failing and restarting during that whole period. Here is what I see as an upload fails and automatically restarts:
Response: 227 Entering Passive Mode (52,23,160,199,117,98).
Response: 150 Opening BINARY mode data connection for file list
Response: 226 Transfer complete
Response: 227 Entering Passive Mode (52,23,160,199,117,83).
Command: STOR US-1584693.bam
Response: 150 Opening BINARY mode data connection for US-1584693.bam
Error: Could not write to transfer socket: ECONNABORTED - Connection aborted
Response: 451 Transfer aborted. Input/output error
Error: File transfer failed after transferring 1,370,750,976 bytes in 363 seconds
Status: Starting upload of F:\Jeremy\ANALYZED_DATA\Project_15903_FUID1025093-2\US-1584693\US-1584693.bam
Status: Retrieving directory listing of "/"...
This may be part of another question, but I thought I was perhaps getting this error for having not enough disk space (EBS). I assumed that of the 3 EBS volumes that were created with cloudman, the 20gb one was for user data (not sure if this is true). So, I made a snapshot, increased the volume to well above what was needed and attached this new EBS volume to my EC2 instance (and detached the older one). The instance worked fine after this, but FTP uploads gave me same error.
Any suggestions? Hopefully, I am just missing something obvious.
In case you are wondering why I am loading .bam files: Someone else ran cuffmerge with my data and I am trying to upload the .bam files and .gtf file to start cuffdiff with cloudman. This seemed reasonable, but I am new to this and not sure if this could be part of the problem.
Thanks for any help you can provide,