Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - jeps

Pages: [1] 2 3 ... 6
Linux / QBitorrent in Centos 7
« on: June 04, 2018, 04:59:07 PM »
I am running some tests. to find out if it is better to change my torrent box from Windows 10 to Linux (Centos 7 as of now).
The qBittorrent version in Centos 7's standard repository is 3.3.7, which is somewhat old.

Can anybody link to a repository with a newer build?
Or link to a site with detailed instructions on how to build a package.

Is Centos the right choice when qBittorrent is the (almost) only program to be used on the box.

Thanks in advance for any input.

Linux / Re: QNAP
« on: May 07, 2018, 08:07:41 PM »
I have a Synology NAs and I have converted to Docker.
Running an Ubuntu machine/Docker on my Synology.

So if you are into Bash you are free to use what you choose.

Windows / Re: WAN IP and router IP showing up in peer list
« on: May 07, 2018, 04:55:15 PM »
I allways disable LSD and still I end up in my own peer-list..
Maybe PEX is to blame, I haven't tried it yet. though.

Linux / Re: Torrents added by Sonarr not downloading
« on: May 07, 2018, 04:21:57 PM »
Last time I Checked (=Sunday) the "Stable" repository, I still got version 4.0.4.
If I tried the "Unstable" repository I got version 4.2.0.alpha

Shouldn't "Stable" repository result in version 4.1.0

The above is from Ubuntu 16.04..

Windows / V4.0.4 (64 bit) and "Last Activity"
« on: February 20, 2018, 05:26:19 PM »
Hi all.

What has happened to this value?
Either I have no value on a torrent or (with active, uploading torrents) so strange value always starting with 18 hours.

Is there something I should do with the settings to fix this?

"Last Activity" (when working  :)) is a really useful information that helps me choose the right torrents to delete, when I am cleaning up.

Windows / Re: How do I save the downloads to a network share?
« on: May 07, 2017, 09:43:48 AM »
You are most likely wrong.

This error was the main reason I stopped using this program some years back.
It is not a "Permission error" or a "corrupt file" error, it is an a feature of the program (so to say)  :)

The only way to store files on a networked drive is to use iSCSI (or something else with the same functionality).
I am using qBittorrrent again and store downloaded files on an iSCSI drive.
It only has 1 downside, iSCSI i somewhat slow on a NAS...

Are you  using Windows 10 by any chance?

Tried with another .RAR packed multy-file torrent, the result was the same type of corruption.
I then tried downloading a few .ISO files (images of different OS), the result was no corruption (the OS from the .ISO installed without a problem).

I hope there will be shed some light on the issue before too long.

Okay, so now I tried downloading the exact same torrent, but this time to a local drive.
The .RAR files was not corrupt in this scenario.

"Their names" is something like "TV show S01E02" = something readable for humans
What I don't want is the hexadecimal name, which don't say sh.. to ordinary people.

I will try and download a torrent to a local drive, but can you confirm the bug when qBittorrent saves to a mapped network drive?
As I explained earlier, I did download the same torrent (that failed in qBittorrent) in µTorrent.
µTorrent found the corruption that qBittorrent had saved, but also managed to download and save the pieces without corruption (unlike qBittorrent).
qBittorrent did find the corruption in a re-check, downloaded the pieces again and then saved a corrupt version again.

The mapped network drive works - in the way that they don't give "fatal I/O errors anymore".

The error I have experienced (now in 2 multi-file (.RAR) - torrents) is as I describe.
qBittorent basically corrupts data in RAR files (the only type that makes a check when you unpack the files I have tried).
I don't know if the same corruption occurs in other file types as-well.

It is not the BT_Back folder I am worried about, it's the folder you use when you enable "copy .torrent file to".
Lets say, like in my check of the file corruption, that I would like to use another bittorrent program.
I would then like to simply load the .torrent file from my own ".torrent folder", but that is impossible given the names they have got.
I am pretty sure, that earlier versions of qBittorrent didn't work that way.


So qBittorrent finally got the "store torrent on mapped network" working, so I can start using it again, yeah!

I have discovered what must be a qBittorrent bug.
When I download a torrent made with several RAR files, one or more of the RAR files are corrupt.
(the same thing doesn't happen with single files, they are always working,)
I then force qBittorrent to recheck, it finds the error and re-downloads the pieces, but... the same RAR file is still corrupt.
When I then load the same torrent in µTorrent it finds the same error and re-downloads the faulty piece(s), and this time the RAR files are working.
This happens whether or not I have preallocate files enabled or not.

Can someone confirm this bug?

It is annoying, that saved .torrent files aren't saved with their "real" names.
It makes it complete impossible to do some clean-up in files not needed.
(that is probably a request  :) )

Thanks for your work, but ...

I tried your experimental build (shared network drives disappearing) and there for would like to stay on qt5
When will qt5 be the new standard for your builds?

Windows / Re: Memory consumption over time
« on: April 11, 2014, 08:58:38 AM »
Why do you keep on stating the obvious?

To sum it up:
I don't care that qBittorrent/libtorrent uses +4 GB of cache, really.
I do care that qBittorrent has a memory/handle leak, that will make it crash after ~100 hours of running.

Windows / Re: Memory consumption over time
« on: April 10, 2014, 07:00:57 PM »
You have not proved conclusively that qBT is using all the memory, you have however shown that Windows is reserving memory when TWO different BitTorrent clients are running, which is not the same thing as the client actually using the memory directly. The BitTorrent  process is the catalyst for the problem, not the actual problem

So no matter how many times you complain about "qBT using memory", it cannot and will not be 'fixed' by changes to the client. UNLESS you consider making the client limit the number of "file handles" it opens to a small number which will severely limit the number of active tasks that can be running.

I haven't shown anything, and I really think you have me confused with someone else in this thread.
And I haven't really complained at all, I have reported an issue that apparently a lot of users are experiencing.

It is qBittorrent (libtorrent) responsibility to work within the Windows framework.
Not the other way around.

Pages: [1] 2 3 ... 6