Re: Need to restore zeroed file
Hmm, the file's names in CHK_encoding seem to be storage index? So let's assume this: - Storage root contains "Documents" - "Documents" contains "Personal" - "Personal" contained the file in question I then need to find the old "Personal" directory "descriptor" where the file is in place, right? signature.asc Description: OpenPGP digital signature ___ tahoe-dev mailing list tahoe-dev@tahoe-lafs.org https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
Re: Need to restore zeroed file
Opps, 16 Bytes, of course. signature.asc Description: OpenPGP digital signature ___ tahoe-dev mailing list tahoe-dev@tahoe-lafs.org https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
Re: Need to restore zeroed file
Ah, I see it. :-( upload.py: --- snip - d = self.original.get_encryption_key() def _got(key): e = AES(key) --- snip - I already looked at get_encryption_key() which may use convergence or a "strongly random 16-bit key" which ends up in variable key. That key is generated by hashing the plain-text file (right?). So I need the plain text file to re-generate the key again ... Or I need the key itself ... :-( signature.asc Description: OpenPGP digital signature ___ tahoe-dev mailing list tahoe-dev@tahoe-lafs.org https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
Re: Need to restore zeroed file
On 07/10/2015 01:09 AM, Daira Hopwood wrote: > Assuming you were using sshfs with Tahoe's SFTP server, there are two > possibilities: > > * The file was actually uploaded and is still linked from the parent > directory that you configured the SFTP server to use. To eliminate any > possible SFTP-related problems, use 'tahoe ls' on that directory URI, > and 'tahoe cp' to copy the file if it is there. > > * The file was never correctly uploaded, in which case it is lost if you > have no other copy. > In my other mail I wrote: --- I have the upload helper active here and CHK_encoding bears 2 files what may match the time (today) when I have tried to save the actual file. Now is there a way to read "private/secret" and "private/convergence" to decode them? If yes, can someone write a script or tell me what to do? --- I think that these two files (both not a ZIP file) are encrypted with secret and convergence? Or what happens with the file when the upload helper is available? signature.asc Description: OpenPGP digital signature ___ tahoe-dev mailing list tahoe-dev@tahoe-lafs.org https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
Re: Need to restore zeroed file
On 07/09/2015 11:33 PM, Daira Hopwood wrote: > This is unclear; do you mean that a file containing the URI got zeroed? I have saved a file through sshfs and all I got was a zero-length file in my mount point. > > is actually the length of the file. Ah, okay. > > You won't be able to brute-force either or . Unless you have a > copy of > the URI somewhere else, the file contents are lost. > Well, I *could* try all possible URIs out, but as Ed said, our sun will die before I have brute-forced key1*key2*file size ... So I have tried another approach, please see my other email. And thank you for replying. :) Regards, Roland signature.asc Description: OpenPGP digital signature ___ tahoe-dev mailing list tahoe-dev@tahoe-lafs.org https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
Re: Need to restore zeroed file
On 07/09/2015 11:22 PM, Ed Kapitein wrote: > Well, without doing the actual math, i think our sun has died before you > can bruteforce key1*key2*9. Okay, so I better try something else. :) > Do you have the storage index for the lost file? that might give you a > fighting change to get the content back. How/where do I get it? > > Kind regards, > Ed > > And please see my other email. :) signature.asc Description: OpenPGP digital signature ___ tahoe-dev mailing list tahoe-dev@tahoe-lafs.org https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
Interrupted upload bears files in CHK_encoding
Hello all, as you may know, I'm in the middle of recovering a lost file due to zeroing. I have the upload helper active here and CHK_encoding bears 2 files what may match the time (today) when I have tried to save the actual file. Now is there a way to read "private/secret" and "private/convergence" to decode them? If yes, can someone write a script or tell me what to do? Regards, Roland signature.asc Description: OpenPGP digital signature ___ tahoe-dev mailing list tahoe-dev@tahoe-lafs.org https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
Re: Need to restore zeroed file
Maybe possible:
cd ~/.tahoe/storage/shares/
find . -type f -exec grep " mutable " {} \;|grep "matches"|cut -d " " -f 3
Then check time stamp of all files.
This will find (on my installation) only directories where the lost file
has been linked in, right?
signature.asc
Description: OpenPGP digital signature
___
tahoe-dev mailing list
tahoe-dev@tahoe-lafs.org
https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
Need to restore zeroed file
Hello all, bad news: One of my files in my storage got zeroed and I don't have the old (working) URI or up-to-date backup (only from 2013). I have currently written a brute-forcer which currently *should* test all possibilities. Sure this needs massive improvement. So I need to know something: 1) Is this URL pattern valid: http://127.0.0.1:3456/file/URI%3ACHK%3A%3A%3A3%3A10%3A/@@named=/ by: = 26 Byte long character consisting of a BASE32 checksum = 52 Byte long character consisting of a BASE32 checksum = Random number from 0 to 9 = The file's name without path 2) Is z_base_32_alphabet or rfc3548_alphabet taken as an alphabet? 3) Do I calculate this correctly? 26 length, each can have 32 different characters (key1) This means 1*32^26 = 1361129467683753853853498429727072845824 possibilities? And 1852673427797059126777135760139006525652319754650249024631321344126610074238976 possibilities for key2? 3) Do I *really* have to brute-force them all to find the correct URI? Or can someone (I don't like to paste brute-forcer publicly) improve the search algorithm? Regards, Roland signature.asc Description: OpenPGP digital signature ___ tahoe-dev mailing list tahoe-dev@tahoe-lafs.org https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
Re: Banana error?
I finally found it. One of the helper URLs were bad (with tcp:interface=) and: tub.location = tcp:interface=192.168.2.4 Had to be commented out. Then it works. Thank you for pointing this out. :) This works now: (and is really fine) [node] nickname = laptop web.port = tcp:3456:interface=192.168.2.4 web.static = public_html tub.port = tcp:8097:interface=192.168.2.4 Regards, Roland signature.asc Description: OpenPGP digital signature ___ tahoe-dev mailing list tahoe-dev@tahoe-lafs.org https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
Re: Banana error?
> > Warning: dependency 'cryptography' (version '0.5.4') found by pkg_resources > not found by import. > Warning: dependency 'six' (version '1.8.0') found by pkg_resources not found > by import. > Warning: dependency 'cffi' (version '0.8.6') found by pkg_resources not found > by import. > Warning: dependency 'pycparser' (version '2.10') found by pkg_resources not > found by import. > > > can you confirm you have these packages installed in your local python > installation? (or simply run pip install all of them) Yes, they are all there and installed as "native" Debian packages. For example: quix0r@sony:~$ ls -l /usr/lib/python2.7/dist-packages/cryptography/ total 652 -rw-r--r-- 1 root root 1174 Aug 21 08:00 __about__.py -rw-r--r-- 1 root root852 Sep 13 13:59 __about__.pyc -rw-r--r-- 1 root root 586712 Aug 21 20:27 _Cryptography_cffi_4ed9e37dx4000d087.i386-linux-gnu.so -rw-r--r-- 1 root root 9584 Aug 21 20:27 _Cryptography_cffi_684bb40axf342507b.i386-linux-gnu.so -rw-r--r-- 1 root root 9584 Aug 21 20:27 _Cryptography_cffi_8f86901cxc1767c5a.i386-linux-gnu.so -rw-r--r-- 1 root root 1464 Aug 21 08:00 exceptions.py -rw-r--r-- 1 root root 2804 Sep 13 13:59 exceptions.pyc -rw-r--r-- 1 root root 4100 Aug 21 08:00 fernet.py -rw-r--r-- 1 root root 4338 Sep 13 13:59 fernet.pyc drwxr-xr-x 5 root root 4096 Sep 13 13:59 hazmat -rw-r--r-- 1 root root892 Aug 21 08:00 __init__.py -rw-r--r-- 1 root root603 Sep 13 13:59 __init__.pyc -rw-r--r-- 1 root root993 Aug 21 08:00 utils.py -rw-r--r-- 1 root root 1067 Sep 13 13:59 utils.pyc quix0r@sony:~$ > I noticed similar odd behavior during my initial attempts at installing > tahoe on windows (linux seems to be much more forgiving). > In fact you may also want to try running setup clean and setup build. I repeated this here, too. No change. > > This may not be the root cause of your issues, but judging from the the > fact that your node cannot even start at this point, it is worth confirming. > Also you are running all of the nodes on your local machine or on > separate machines? What else has changed in your environment? Is > this a new installation or has this setup been running for some time? They run on separate machines and the setup for a long time with no problems. Thanks for helping, still I look for a fix. Roland signature.asc Description: OpenPGP digital signature ___ tahoe-dev mailing list tahoe-dev@tahoe-lafs.org https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
Re: Banana error?
On 09/27/2014 08:14 PM, Roland Haeder wrote:
> On 09/27/2014 07:41 PM, jg71 wrote:
>> I'd like to remind folks of ticket #57
>> https://tahoe-lafs.org/trac/tahoe-lafs/ticket/57
>> logging: compress/truncate/encode/decode/format for human readability
>> and privacy
>>
>> Please think carefully about just adding incident logs to Tahoe
>> tickets or share them publicly (at all?) - they often include
>> precarious info about your grid (IP addresses and ports of storage
>> nodes, introducer location, etc.) - please consider manually
>> scrubbing such info
>>
> Cannot Tahoe "anonymize" these files, e.g. replacing ids with abc123,
> changing IP addresses to 1.2.3.4 and such?
>
>
>
> ___
> tahoe-dev mailing list
> tahoe-dev@tahoe-lafs.org
> https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
>
Nothing here?
I'm still getting those error messages:
---
File "/usr/lib/python2.7/dist-packages/foolscap/referenceable.py", line
821, in decode_location_hints hint = ("tcp", fields["host"],
int(fields["port"])) exceptions.KeyError: 'host'
---
This happens on introducer side.
signature.asc
Description: OpenPGP digital signature
___
tahoe-dev mailing list
tahoe-dev@tahoe-lafs.org
https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
Re: Banana error?
On 09/27/2014 07:41 PM, jg71 wrote: > I'd like to remind folks of ticket #57 > https://tahoe-lafs.org/trac/tahoe-lafs/ticket/57 > logging: compress/truncate/encode/decode/format for human readability > and privacy > > Please think carefully about just adding incident logs to Tahoe > tickets or share them publicly (at all?) - they often include > precarious info about your grid (IP addresses and ports of storage > nodes, introducer location, etc.) - please consider manually > scrubbing such info > Cannot Tahoe "anonymize" these files, e.g. replacing ids with abc123, changing IP addresses to 1.2.3.4 and such? signature.asc Description: OpenPGP digital signature ___ tahoe-dev mailing list tahoe-dev@tahoe-lafs.org https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
Re: Banana error?
Attached is an incident logfile from node 1 (Gentoo). incident-2014-09-27--15-10-22Z-s54wbfy.flog.bz2 Description: Binary data signature.asc Description: OpenPGP digital signature ___ tahoe-dev mailing list tahoe-dev@tahoe-lafs.org https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
Re: Banana error?
On 09/27/2014 03:35 PM, Daira Hopwood wrote:
> On 27/09/14 09:18, Roland Haeder wrote:
>> On 09/27/2014 01:53 AM, Daira Hopwood wrote:
>>> tahoe --version-and-path
>> I can paste from all nodes + introducer:
>>
>> introducer:
>> http://pastie.org/9598990
>>
>> node 1: ("external"; Gentoo)
>> http://pastie.org/9599004
>>
>> node 2: ("external"; Debian)
>> http://pastie.org/9599005
>
> OK thanks. Which node's log did you find the unhandled error in?
> Was it only in the log, or was there any other observed misbehaviour?
>
I found similar errors on all nodes. Now one is no longer starting:
http://pastie.org/9599865
And on node 2 I have over 24,000 (!) incident reports.
Attached is the latest.
incident-2014-09-27--14-36-48Z-br5uqmi.flog.bz2
Description: Binary data
signature.asc
Description: OpenPGP digital signature
___
tahoe-dev mailing list
tahoe-dev@tahoe-lafs.org
https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
Re: Banana error?
On 09/27/2014 01:53 AM, Daira Hopwood wrote:
> tahoe --version-and-path
I can paste from all nodes + introducer:
introducer:
http://pastie.org/9598990
node 1: ("external"; Gentoo)
http://pastie.org/9599004
node 2: ("external"; Debian)
http://pastie.org/9599005
Roland
signature.asc
Description: OpenPGP digital signature
___
tahoe-dev mailing list
tahoe-dev@tahoe-lafs.org
https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
Re: Banana error?
A locally (localhost) can introduce but no "outside" (LAN). signature.asc Description: OpenPGP digital signature ___ tahoe-dev mailing list tahoe-dev@tahoe-lafs.org https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
Banana error?
Hello all,
I got the attached error message.
Roland
2014-09-27 00:58:46+0200 [Negotiation,710,192.168.2.5]
Banana.reportReceiveError: an error occured during receive
2014-09-27 00:58:46+0200 [Negotiation,710,192.168.2.5] Unhandled Error
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/twisted/internet/tcp.py", line
220, in _dataReceived
rval = self.protocol.dataReceived(data)
File "/usr/lib/python2.7/dist-packages/twisted/protocols/tls.py", line
422, in dataReceived
self._flushReceiveBIO()
File "/usr/lib/python2.7/dist-packages/twisted/protocols/tls.py", line
392, in _flushReceiveBIO
ProtocolWrapper.dataReceived(self, bytes)
File "/usr/lib/python2.7/dist-packages/twisted/protocols/policies.py",
line 120, in dataReceived
self.wrappedProtocol.dataReceived(data)
--- ---
File "/usr/lib/python2.7/dist-packages/foolscap/banana.py", line 639, in
dataReceived
self.handleData(chunk)
File "/usr/lib/python2.7/dist-packages/foolscap/banana.py", line 870, in
handleData
self.handleClose(count)
File "/usr/lib/python2.7/dist-packages/foolscap/banana.py", line 1068, in
handleClose
obj, ready_deferred = child.receiveClose()
File "/usr/lib/python2.7/dist-packages/foolscap/referenceable.py", line
249, in receiveClose
self.url)
File "/usr/lib/python2.7/dist-packages/foolscap/broker.py", line 351, in
getTrackerForYourReference
tracker = trackerclass(self, clid, url, interfaceName)
File "/usr/lib/python2.7/dist-packages/foolscap/referenceable.py", line
292, in __init__
url_tubid = SturdyRef(url).getTubRef().getTubID()
File "/usr/lib/python2.7/dist-packages/foolscap/referenceable.py", line
897, in __init__
decode_furl(url)
File "/usr/lib/python2.7/dist-packages/foolscap/referenceable.py", line
850, in decode_furl
location_hints = decode_location_hints(hints)
File "/usr/lib/python2.7/dist-packages/foolscap/referenceable.py", line
821, in decode_location_hints
hint = ("tcp", fields["host"], int(fields["port"]))
exceptions.KeyError: 'host'
signature.asc
Description: OpenPGP digital signature
___
tahoe-dev mailing list
tahoe-dev@tahoe-lafs.org
https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
Re: How to let these ports listen only on one device?
On 09/13/2014 11:36 PM, David Stainton wrote: > https://tahoe-lafs.org/trac/tahoe-lafs/browser/docs/configuration.rst#overall-node-configuration > > tub.port must be set to something like: tcp:interface=127.0.0.1:7789 > tub.port = tcp:8097:interface=192.168.x.y tub.location = tcp:interface=192.168.x.y This finally worked. Thank you for helping. :) signature.asc Description: OpenPGP digital signature ___ tahoe-dev mailing list tahoe-dev@tahoe-lafs.org https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
Re: How to let these ports listen only on one device?
On 09/13/2014 11:36 PM, David Stainton wrote: > https://tahoe-lafs.org/trac/tahoe-lafs/browser/docs/configuration.rst#overall-node-configuration > > tub.port must be set to something like: tcp:interface=127.0.0.1:7789 > These were my settings: tub.port = 8097 tub.location = 192.168.2.4:8097,127.0.0.1:8097 Still it is listening to 0.0.0.0:8097 signature.asc Description: OpenPGP digital signature ___ tahoe-dev mailing list tahoe-dev@tahoe-lafs.org https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
How to let these ports listen only on one device?
Hello together, I run Tahoe-LAFS on my local network on all my computers (because of their storage capacity). This also includes Laptops (Debian, Gentoo) with WiFi cards. I then run batman-adv to let the laptops mesh a little. I have now found 1 Tahoe-LAFS port open to 0.0.0.0 which means they are accessible from outside through my WiFi cards. Of course, I can turn them off but then I cannot mesh. :) So here are the ports: laptop ~ # netstat -lnp|grep "0 0.0.0.0:" tcp0 0 0.0.0.0:80970.0.0.0:* LISTEN 12239/python2.7 laptop ~ # Is there a way to only let it open to my LAN (cable) network, e.g. a tweak in config file? Best regards, Roland signature.asc Description: OpenPGP digital signature ___ tahoe-dev mailing list tahoe-dev@tahoe-lafs.org https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
Tub listens on *all* devices?
Hello all, I run Tahoe-LAFS on my laptops. Once I activate the WLAN chip, it is listens on it, too. Is there a way to force Tub not to listen on all (0.0.0.0) devices but only on specific? Here is my setting (IP altered): tub.port = 8097 tub.location = 192.168.x.y:8097,127.0.0.1:8097 Roland signature.asc Description: OpenPGP digital signature ___ tahoe-dev mailing list tahoe-dev@tahoe-lafs.org https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
Re: If the machine run the introducer down,what can i do
On 03/17/2014 10:08 PM, Zooko Wilcox-OHearn wrote:
> That's right. If you have a backup of the introducer's private keys
> then you could set up a new introducer that would have the same FURL.
> If not, then you'll have to put in the new introducer's FURL to each
> storage server and each client.
>
> The multi-introducer ticket that str4d mentioned is ticket #68:
>
> https://tahoe-lafs.org/trac/tahoe-lafs/ticket/68# implement
> distributed introduction, remove Introducer as a single point of
> failure
>
> The state of that ticket is: "test-needed" — it is waiting for someone
> to write unit tests that test the code changed by the patch.
>
> Regards,
>
> Zooko
> ___
> tahoe-dev mailing list
> tahoe-dev@tahoe-lafs.org
> https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
>
Still the chicken-egg-problem needs to be solved:
How can a virgin node get "knowledge" about the network without
bootstrappers? :-) Of course, you can have multiple bootstrap nodes
("introducer" in your terms) so you have ruled out the SPoF (single
point of failure) but still privacy matters are left: all introducer
owner know about the network's structure, at least which IPs run the
storage nodes.
Okay, maybe not a topic here, as Tahoe-LAFS != Freenet.
So a good advice for you @topic start is that you run your introducer on
a RAID1 with at least 3 physical drives and none are SSDs please (SSD =
electronic method = shorter life of the "disk", HDD = magnetic =
longer-lasting storage).
Regards,
Roland
signature.asc
Description: OpenPGP digital signature
___
tahoe-dev mailing list
tahoe-dev@tahoe-lafs.org
https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
Re: Videos watchable from storage grid
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/23/2014 12:05 PM, Oleksandr Drach wrote: Hello Oleksandr, here it is: - - Node 1: Quad Core 2.5 GHz, 4 GB RAM, encrypted home Linux-RAID1 - - Node 2: Single Core AMD 64 3500+ (2.2 GHz), 4 GB RAM, IDE/SATA - - Node 3: Single Core 1.7 GHz (Laptop), ~770 MB RAM, encrypted root IDE - - Node 4: Dual Core 1.6 GHz (Laptop), ~770 MB RAM, encrypted root SATA All run on Debian Linux, except 3, that runs on Gentoo. But this is a length-comparison, isn't it? ;-) Roland -BEGIN PGP SIGNATURE- Version: GnuPG v1 iEYEARECAAYFAlLhXWEACgkQty+BhcbHvXgI0ACdESphvfv7C85BoJ881GDyd7nQ CRMAn0gQpcy23cSHX/XgsSWAxJ7M0+xL =uFND -END PGP SIGNATURE- ___ tahoe-dev mailing list tahoe-dev@tahoe-lafs.org https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
Videos watchable from storage grid
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello all, I would like to let you know that I have watched the first movie clip (VIDEO: [H264] 1280x720 0bpp 25.000 fps 2498.6 kbps (305.0 kbyte/s)) from my storage grid through sshfs. Greetings, Roland -BEGIN PGP SIGNATURE- Version: GnuPG v1 iEYEARECAAYFAlLgLScACgkQty+BhcbHvXgc6gCeMX+rzLyzeZBUCNY6R66n/ILZ MV8Aniq2nRSslLTEcSMa1gdcPm+6ViWo =HPEV -END PGP SIGNATURE- ___ tahoe-dev mailing list tahoe-dev@tahoe-lafs.org https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
Fwd: Re: Rebalancing
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Please reply to all, so the mailing list can read it. - Original Message Subject:Re: Rebalancing Date: Sun, 5 Jan 2014 16:19:01 -0500 From: Paul Rabahy To: Roland Haeder I feel your pain and have manually rebalanced several files on the test grid by deleting files from the shares folders. I don't recommend this method because deleting the wrong shares can result in entire files being gone. There are plans to improve this behavior in the future. https://tahoe-lafs.org/trac/tahoe-lafs/ticket/699 https://tahoe-lafs.org/trac/tahoe-lafs/ticket/543 On Sun, Jan 5, 2014 at 2:02 PM, Roland Haeder mailto:r.hae...@web.de>> wrote: Hello all, I use Tahoe-LAFS for storing distributed my pictures, OGGs (music mainly) on my home network with a local introducer. Now I have added another node, which is a "rescued" Laptop from Fujitsu Siemens with 100 GB HDD, 750 MB RAM and 1.6 GHz CPU (single) from being almost thrown away by my parents. I have run "tahoe create-node on it and copied the tahoe.cfg from an other node + changed nickname and fired it up. Then I have entered the following: $ tahoe deep-check --repair --add-lease --verbose myshare: which repaired 2 shares. This, of course, does not rebalance. Now I would like know how rebalancing is possible without re-uploading all. Is there a way or something planed like: $ tahoe rebalance --verbose myshare: ??? And happy new year. :-) Regards, Roland ___ tahoe-dev mailing list tahoe-dev@tahoe-lafs.org <mailto:tahoe-dev@tahoe-lafs.org> https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.15 (GNU/Linux) iEYEARECAAYFAlLK+K0ACgkQty+BhcbHvXjv8ACfc+/OxXDeLJmR5qbCUSwyEdzx wc8AnRwqeYdeAXf1cDIRKDBMXar8FsSX =8VBY -END PGP SIGNATURE- ___ tahoe-dev mailing list tahoe-dev@tahoe-lafs.org https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
Rebalancing
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello all, I use Tahoe-LAFS for storing distributed my pictures, OGGs (music mainly) on my home network with a local introducer. Now I have added another node, which is a "rescued" Laptop from Fujitsu Siemens with 100 GB HDD, 750 MB RAM and 1.6 GHz CPU (single) from being almost thrown away by my parents. I have run "tahoe create-node on it and copied the tahoe.cfg from an other node + changed nickname and fired it up. Then I have entered the following: $ tahoe deep-check --repair --add-lease --verbose myshare: which repaired 2 shares. This, of course, does not rebalance. Now I would like know how rebalancing is possible without re-uploading all. Is there a way or something planed like: $ tahoe rebalance --verbose myshare: ??? And happy new year. :-) Regards, Roland -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.15 (GNU/Linux) iEYEARECAAYFAlLJrF0ACgkQty+BhcbHvXhBFgCfa1fhZb/+4pc04aT/+FL33d2r JW4AoJJ7QBtPYvmyEPuPc/c+qqParwjQ =K2PU -END PGP SIGNATURE- ___ tahoe-dev mailing list tahoe-dev@tahoe-lafs.org https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
Re: [tahoe-dev] Newbie problems
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/03/2013 07:57 PM, Zooko Wilcox-OHearn wrote: > option a) Someone volunteers to become the Official Tahoe-LAFS.org > Test Grid Wrangler, and make sure there is a reliable introducer. > That person's name and email address appears next to the introducer > furl on the wiki. Bad idea. I have no good experience with this. I had someone else running a wiki for my small project. After the second unreported (he didn't say anything to me) disappearance, I removed all "official" links to his wiki site (as it was domain-parked) and now I run an own wiki. > > option b) We edit running.rst to remove any mention of the > existence of a Public Test Grid and instead have it instruct people > in how to set up their own test grid. Better, then people learn how to do it. Also, the "test" grid might be abused to host illegal stuff there from Hollywood movies, pr0n to how to make drugs. So I would vote for b). Regards, Roland -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlEPR/YACgkQty+BhcbHvXjpagCeNrlg9XeyXntkK2qBa2oZvuua IGoAnRki/6fR8CFEyEEg4hPfDXZB657r =q65g -END PGP SIGNATURE- ___ tahoe-dev mailing list tahoe-dev@tahoe-lafs.org https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
Re: [tahoe-dev] hello
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/30/2012 04:25 PM, han zheng wrote: > Hi, Is there a way to directly upload a local file to the "tahoe > cloud" not using the web server? You may want to use FUSE or SFTP to do that if you cannot use the "tahoe" command-line tool. Regards, Roland -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlCP9+sACgkQty+BhcbHvXi1tQCgh3/FV9oIiSWOkEz/B3I6f2no 60kAn0M7odwSnRX545FBc5gTqgt9Ehim =JwR+ -END PGP SIGNATURE- ___ tahoe-dev mailing list tahoe-dev@tahoe-lafs.org https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
