Posted
9 months
ago
by
dneb
I was using Spaceblock last night and I was attempting to list the contents of one of my buckets. Now I have the bucket divided into a folder type structure, and accessing the other "folders" was successful. But when I tried to access a
... [More]
particular "folder" that has probably 10,000+ objects in it, Spaceblock just sat there with it's loading screen. I left the application open (don't know why), and after about an hour my system began to run dreadfully slow. I opened the Task Manager and lo and behold, Spaceblock was using 1.3 GB of my memory. I have attached screenshots for those interested in helping debug this issue (urls for those that don't trust the dowload). Here are the issues I'd like addressed:
1. Why can't I get a file listing when a "folder" has a lot of objects in it?
2. Why is Spaceblock using so much memory?
Thanks!
http://www.kmg.net/pub/spaceblock-1.png
http://www.kmg.net/pub/spaceblock-2.png
http://www.kmg.net/pub/spaceblock-3.png
Comments: ** Comment from web user: dneb ** I had something somewhat similar. I was trying to delete a gigantic bucket (a JungleDisk backup bucket). No idea how many files, but it's huge. It ran all night and in the morning the process was using 7.5GB of memory. [Less]
Posted
over 1 year
ago
by
redwards1966
While using the MSBuild S3Upload task I found that UNC paths don't work at all so I was required to map a drive to the network location instead.
Posted
almost 2 years
ago
by
c0d3
Uploading large files to Azure Blob service returns this error:
<?xml version="1.0" encoding="utf-8"?><Error><Code>RequestBodyTooLarge</Code><Message>The request body
... [More]
is too large and exceeds the maximum permissible limit.</Message><MaxLimit>67108864</MaxLimit></Error>
Comments: ** Comment from web user: c0d3 ** The request body is to large - error may be caused by trying to upload the same file many times. When files are uploaded it is uploaded in eg. 64KB blocks, and Azure may have a MaxLimit for how many blocks can be uploaded, when this limit is reached, the error is thrown. Blocks are still in the blobstorage but uncomittet, I fixed this in one of my projects by deleting a file blob if the stream prosition is set to 0.
container.DeleteBlob(blobProperties.Name) and then uploaded the same file with a block size of 1MB. Hope this helps. [Less]
Posted
almost 2 years
ago
by
_TFSSERVICE
Checked in by server upgrade
Posted
over 2 years
ago
by
jaybo_nomad
The Nov 2009 release includes a pseudo root folder called "$root". Items in this folder appear in the root of the storage tree.
I can't seem to create a container of this name by right clicking and selecting "New Folder...".