You are not logged in.
Pages: 1
On the off chance anyone is considering using echofs for remote storage (I am, I'm not affiliated, and I've only just signed up so can't speak to service level), then be aware that you need to have the following installed (this differs from the echofs website's instructions, hence the post):
fuse
davfs2
ntfs-3g
dkms
cl
Last edited by clearloon (2012-05-03 17:09:22)
Offline
Hi there,
I am trying to get this to work but I just cannot write to the drive from arch.
How exactly did you set it up?
Thanks!
Offline
So I was never able to get this going with FUSE. No matter what I tried. Everytime I would attempt to copy or write to the device it told me the file already existed. On the suggestion of a friend I contacted EchoFS Support and asked them to convert my storage from WebDav to NBD. To get it working on my system I simply did the following:
pacman -S nbd
nohup nbd-client dav.echofs.com 9440 /dev/nbd0 -persist &
mke2fs -j -b 1024 /dev/nbd0
mkdir -p /mnt/nbd0
mount /dev/nbd0 /mnt/nbd0
df -aH /mnt/nbd0
[the-swan] (~) >>> df -aH /mnt/nbd0
Filesystem Size Used Avail Use% Mounted on
/dev/nbd0 31G 34M 30G 1% /mnt/nbd0
Offline
You probably need to use the following in /etc/davfs2/davfs2.conf:
use_locks 0
if_match_bug 1Without use_locks I couldn't write any file (also happens with other webdav cloud servers) and without if_match_bug all files would end up in lost+found.
R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K
Offline
Thanks for the tip. If I get another EchoFS account I will try to webDav access again. I am liking the NBD cause I can format it with my own file-system.
- Ryan
Offline
After reading this i've set up an nbd device with echofs, it works good.
But i wonder if i will be forced to encrypt the filesystem, as no login/password information is required to mount that nbd device...
--edit
Got the answer from echofs techincal support; seems that everybody can mount your device if you're not connected to it, so encryption is needed, but they still can format/delete/corrupt your nbd device.
He said that probably in the future they'll provide openvpn access to paying customers.
Last edited by kokoko3k (2012-10-18 14:13:16)
Help me to improve ssh-rdp !
Retroarch User? Try my koko-aio shader !
Offline
They could instead start using the _new_ way to export devices, by name.
If they assign a name that is hard enough to guess then possible attackers would have a much harder time finding the devices.
Still it's nice to have something like this to play, using ecryptfs on top of it now.
R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K
Offline
That would be nice, could you be more specific so that i can forward that info to them?
Help me to improve ssh-rdp !
Retroarch User? Try my koko-aio shader !
Offline
As far as I know they are using version 2.9.11, at least it is what they say in the email with instructions. That version is from May 2008 and doesn't support exporting by name, only port, however newer versions (2.9.17 and newer) can also emulate this. They should probably update their nbd package to something more recent but if they haven't done so there is probably a good reason.
Since you are using Arch just look at 'man 5 nbd-server', everything is explained there and there are a few examples.
R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K
Offline
Thanks, let's see if they will use it.
Help me to improve ssh-rdp !
Retroarch User? Try my koko-aio shader !
Offline
Thanks, let's see if they will use it.
Did you get any response about them exporting by name instead of exporting by port?
R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K
Offline
I've got non answer to my last email, sorry.
Help me to improve ssh-rdp !
Retroarch User? Try my koko-aio shader !
Offline
Pages: 1