Creating a directory inside the container âdefaultâ works. I just tested so hubiC works (at least a bit).
But creating a root âdirectoryâ still fails.
Is âmkdirâ the correct command to create a new container?
I have exactly the same problem. I wonder how to analyze the problem in more detail.
I want to make a backup of a big directory in hubic.
I do not want to copy my files to default, because I am using hubic syncing tool for a small set of small files but it syncs everything in default including my backup. As a result it overloads my computer.
âhubic backup createâ worked on some directories but began to fail with ânetwork errorâ and is thus useless.
I also installed svfs but it seemed to be on early development phase, beyond my capabilities to use it,.
It seems to me that many have tried to contact hubic on this and many other issues but no one has succeeded. I will continue trying to get in contact with them.
The problem is still present. Against my better judgment but for lack of options Iâm trying Hubic too. The web interface is childish and barren. I managed to remove hubic.com from âApplications connected to your accountâ and lost access temporarily to the web interface (probably until a cron job came and eventually added the application back (most likely Iâm not the first that tries to kill himself).
tried rclone, and have same problems. i do have hubic 12,5TB but havent use long time.
problem is File.Open failed: open for read: HTTP Error: 500: 500 Internal Error
support of hubic is terrible read hubic forums and you see ppl complaining about support they not answer
I donât think hubic lets you create anything outside of the default container by design. Your account is tied to your default container, and hubic doesnât give you access to create other containers. Hubic is a wrapper on SWIFT, not SWIFT itself.
And thereâs really not reason for multiple containers, if youâre just using it for storage and rclone. The directory structure emulation works fine for file organization, IMHO.
I have created containers in the past with hubic - it definitely should work. If you are a paying customer send them the evidence above with the official swift client!
Work arround by mounting your hubic root âhubic:â with svfs, then do a mkdir in the root. You can check with ârclone lsd hubic:â to make sure it is there.
> mount |grep hubic
hubic: on /media/hubic type fuse.svfs (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other)
> cd /media/hubic/
/m/hubic> mkdir borg
> rclone lsd hubic:
0 2017-08-19 12:52:18 0 borg
0 2017-08-19 12:52:18 0 borg_segments
54811888 2017-08-19 12:52:18 10 default
0 2017-08-19 12:52:18 0 default_segments
.
.
.
You are right the PUT request works fine every time.
However rclone normally checks the container exists first using HEAD, like this. It does this so that a limited permission user can use a container created by a higher permission user. (This isnât supported by hubic though.)
This is the call which is hanging, or failing, which really should work!
Iâve changed the hubic module to not do this check (and left the other swift providers alone), so hopefully this should fix it. I view this as a work-around for a busted swift implementation at Hubic, but if it gets rclone working for people then Iâm happy
