[transmission] Transmission 1.76 + DHT download and discussion (OLD THREAD)

[nkostman]

A-110 with 1.61-1 and 1.71 were very stable for me up to speeds nearing 2MB/s with several torrents going. 1.72 is just not working well for me at all. Crashing left and right at low speeds (under 500 KB/s) What's the deal? Anyone else experiencing this?

[wasssu]

(06-02-2009 06:55 PM)enterfornone Wrote:  @SpiderGW: It does look exactly like Transmission

Verifying of 3.5 GB can take looooong.

This is a media box, not a computer. Be sure to always shutdown the player properly, to avoid constant verifying. Every time the client was not shutdown properly at the next start will verify all local data.

What do you mean by shutdown the player properly?

[Peppin]

(06-18-2009 07:56 AM)wasssu Wrote:  What do you mean by shutdown the player properly?

Use remote "Standby Button" + "Delete" button.

[hdfan]

(06-18-2009 01:44 AM)bloodflower Wrote:  after checking the tickets closed in 1.72, i find the info:
Special preallocation for small headless devices - to prevent fragmentation

does it mean that 1.72 finally resolve the file fragment problem of NMT?

Sorry for late reply (had to do some testings). Yes, this version resolves fragmentation problem. You should set preallocation=2 in settings.json file to enable it.

WARNING! With preallocation=2, there'll be a long delay after you upload torrent file and before actual download begins (around 2-2.5 min for 10Gb). This is normal, the files are being preallocated. Web interface and Transmission Remote programs will also be unresponsive. Don't reboot your NMT! The download will continue after preallocation is over.

[Novox]

One question about the newest transmission (1.72), I have uploaded the torrent file into it then let's it start the torrent. I see that the program need to allocate for the space first before it can download the file. Sometime this make transmission webui non-responsible until the program finished allocate the disk.

Is it possible to config transmission to work like uTorrent?? Download and allocate in the same time not to allocate first then download?

[Bytec]

(06-22-2009 08:29 AM)Novox Wrote:  One question about the newest transmission (1.72), I have uploaded the torrent file into it then let's it start the torrent. I see that the program need to allocate for the space first before it can download the file. Sometime this make transmission webui non-responsible until the program finished allocate the disk.

Is it possible to config transmission to work like uTorrent?? Download and allocate in the same time not to allocate first then download?

Edit your settings.json file and set preallocation acordingly.

preallocation: Number (0 = Off, 1 = Fast, 2 = Full (slower but reduces disk fragmentation), default = 1)

You may also want to read this wiki.

[galleyrod]

Hi all!

I have a small problem regarding this app. I have tried installing both versions 1.71 and 1.72 via CSI and as for this part without any problems, but whenever I try to open it via Popcorn using a remote I get an error message "request cannot be processed. press return." web gui and even logging to it using my symbian mobie is working but the gaya interface (is this the right name for it?) does not start.

I did also stop the torrent protocol, restart NMT a couple of times, reinstal the app and reenable the protocol but without any luck.

Is there an easy way to do it or at least a hint how to make it 100% working as for all the gui's?

thanks

*EDIT

Solved the problem myself. It was a Vista problem, don't know how but CSI is not working as it should on this system. After installing 1.71 via CSI on XP - no errors and it works like a charm.

[nianoniano]

Is it possible download version 1.61 of transmission?

I just installed 1.72 and now one private tracker don't allow this client, so I would like return to version 1.61 that worked fine to me, but CSI don't have that version.

Thanks in advance

[Ger Teunis]

(06-22-2009 05:14 PM)nianoniano Wrote:  Is it possible download version 1.61 of transmission?

I just installed 1.72 and now one private tracker don't allow this client, so I would like return to version 1.61 that worked fine to me, but CSI don't have that version.

Download this file:
http://repository.nmtinstaller.com/Appli...61-nmt.zip

and install it using CSI via File.. Install from file and you should be fine again.

[bloodflower]

(06-21-2009 05:58 PM)hdfan Wrote:  Sorry for late reply (had to do some testings). Yes, this version resolves fragmentation problem. You should set preallocation=2 in settings.json file to enable it.

WARNING! With preallocation=2, there'll be a long delay after you upload torrent file and before actual download begins (around 2-2.5 min for 10Gb). This is normal, the files are being preallocated. Web interface and Transmission Remote programs will also be unresponsive. Don't reboot your NMT! The download will continue after preallocation is over.

are you sure that we should set the preallocation=2?
i see the ticket discussion in the official site, does it mean we should set the preallocation=3?

" Replying to charles:

Why do we need a new preallocation type? What if we were to just add another "if( !success )" test that contained the write-in-a-loop code?

I've done it as a separate option for two reasons: 1) I wanted everything to work as before with old settings, to be sure that nobody will be harmed by this patch; 2) More importantly, I'm not completely sure that fallocate and/or posix_fallocate are absent on our platforms or that they return non-zero (fail). I'm even quite sure that (one of them or both) return 0 because files ARE preallocated (however, in a sparse mode, prone to fragmentation). However, I may be wrong here.

I'll ask Ger Teunis to build one more version, so that I could test this patch on NMT as well. "

[kamuranmulayim]

(06-18-2009 05:22 AM)nkostman Wrote:  A-110 with 1.61-1 and 1.71 were very stable for me up to speeds nearing 2MB/s with several torrents going. 1.72 is just not working well for me at all. Crashing left and right at low speeds (under 500 KB/s) What's the deal? Anyone else experiencing this?

I have used all transmission versions since 1.4x, 1.71 was the most stable and I had maximum speed. I updated to 1.72 and my speed went town so switched back to 1.71.

[hdfan]

(06-23-2009 01:49 AM)bloodflower Wrote:  are you sure that we should set the preallocation=2?
i see the ticket discussion in the official site, does it mean we should set the preallocation=3?

" Replying to charles:

Why do we need a new preallocation type? What if we were to just add another "if( !success )" test that contained the write-in-a-loop code?

I've done it as a separate option for two reasons: 1) I wanted everything to work as before with old settings, to be sure that nobody will be harmed by this patch; 2) More importantly, I'm not completely sure that fallocate and/or posix_fallocate are absent on our platforms or that they return non-zero (fail). I'm even quite sure that (one of them or both) return 0 because files ARE preallocated (however, in a sparse mode, prone to fragmentation). However, I may be wrong here.

I'll ask Ger Teunis to build one more version, so that I could test this patch on NMT as well. "

No, you should set preallocation=2; preallocation=3 will crash Transmission.

[enterfornone]

I have two requests here, please consider them:
1. Ger, is it possible to set preallocation=2 as default? Thus we won't need to edit a file on the box (which for noobs like me is difficult)
2. Is it possible to make a GUI to modify the settings.json through a webservice? This will be immensely helpful (again for people like me, who are not comfortable with telneting the NMT).

[Novox]

I have installed Transmission for both 1.71 and 1.72 via CSI, preallocation is set to 2 as default.

[Ger Teunis]

(06-27-2009 08:42 AM)enterfornone Wrote:  I have two requests here, please consider them:
1. Ger, is it possible to set preallocation=2 as default? Thus we won't need to edit a file on the box (which for noobs like me is difficult)
2. Is it possible to make a GUI to modify the settings.json through a webservice? This will be immensely helpful (again for people like me, who are not comfortable with telneting the NMT).

I do not think we need to change the default behavior here and follow the default settings of the transmission crew. The full allocate (2) will cause big slowdowns and this will confuse the majority of users because the UI will become unresponsive for a while. Most of the users do not see the fragmentation issues that bad.

Regarding the UI> that would be great. Perhaps shurup can pick this up again. If anyone with spare time is feeling lucky: you can always submit changes to me, I would be happy to pack them with the next release.