[tahoe-dev] ODROID-U2 (linux) tahoe-lafs 1.10.0 initial report
Garonda Rodian
deepside at hotmail.com
Thu Oct 17 03:24:39 UTC 2013
In the directory with setup.py, try
python setup.py trial
or, to see more options, none of which I've played with except build :)
python setup.py --help-commands
From: jason.johnson at p7n.net
To: deepside at hotmail.com; tahoe-dev at tahoe-lafs.org
Subject: RE: [tahoe-dev] ODROID-U2 (linux) tahoe-lafs 1.10.0 initial report
Date: Wed, 16 Oct 2013 21:55:11 -0500
By trial what do you mean? Is there a setup someplace I can test it? I have done several every bit verify operations. The biggest one being on a folder I had to make healthy again. I am not uploading files larger then 1g currently. I would like to put a monitor of some kind on the bones. So far they are running well. What would you suggest I use for monitoring them? I ask because there are lots of tools and I would like to stay within tahoe dev realm of things.Here is a pic of it for shows and such. There is a camera in the middle for taking peoples pics that stare at it for more than a few min. That’s running motion. Jason From: Garonda Rodian [mailto:deepside at hotmail.com]
Sent: Wednesday, October 16, 2013 8:54 PM
To: Jason Johnson; tahoe-dev at tahoe-lafs.org
Subject: RE: [tahoe-dev] ODROID-U2 (linux) tahoe-lafs 1.10.0 initial report How fast does the Atom blade run the trial? I'm assuming the BeagleBone Blacks can't complete it due to lack of RAM.
Do the BeagleBone Blacks have a hardware watchdog?
Separately, how many "Every bit" verify operations have you done, and how well did they go?
For anyone else trying an ODROID-U2, I'm using the image from
I found out you have to do cp /boot/boot-hdmi-1080p60hz.scr /boot/boot.scr in order to get HDMI working properly at 1920x1080. I'm still working on getting files to it, after which I should be able to really try some intertesting!
Are there any benchmarking modes for tahoe-lafs? I'd like to see the throughput for the encryption step, and for the zfec step, and the hashing, etc., to be able to compare setups.Date: Wed, 16 Oct 2013 09:16:58 -0500
From: Jason.Johnson at p7n.net
To: deepside at hotmail.com; tahoe-dev at tahoe-lafs.org
Subject: RE: [tahoe-dev] ODROID-U2 (linux) tahoe-lafs 1.10.0 initial report
This is cool! Currently I have 8 beaglebone blacks and a small Atom blade as the introducer and helper. I am looking for people to connect to my grid for testing. I even took the hard drive out of the introducer and one node formated them and put tahoe 1.10 i was able to repair the grid no prob.
On 16/10/13 01:28:54,
Garonda Rodian <deepside at hotmail.com> wrote:My ODROID-U2, Debian Wheezy, LXFE has successfully arrived, booted from MicroSD, and run.
python setup.py build failed just after it didn't find tahoe-deps, until I installed my usual set of packages (including, but not limited to, python-dev), after which it worked fine.
python setup.py trial succeed with 6 skipped and 2 expected failures in something over 1500 seconds, typically using 100% of one out of four cores, and the maximum amount of total RAM in use I happened to see (htop) was on the order of 561MB - since it has 2GB of RAM, that's more than fine.
Further testing to follow - I have high hopes it can serve as an introducer + storage nodes, or even a helper/client gateway. If I can get a Gigabit USB2 card working, perhaps it'll even break the 10MB/s limit as a storage node!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20131017/1da0c5db/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 35588 bytes
Desc: not available
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20131017/1da0c5db/attachment-0001.jpg>
More information about the tahoe-dev
mailing list