#969 closed bug (WontFix)
Full allocation allocates for files not selected to download
Reported by: | tim.kornhammar@gmail.com | Owned by: | andar |
---|---|---|---|
Priority: | major | Milestone: | |
Component: | Unknown | Version: | 1.2.0_dev |
Keywords: | Cc: |
Description
When using full allocation with torrents that have multiple files. If I only select to download one file (all others set to "do not download"), it still allocates for the close by torrents in the file segments. I understand it is because segments can overlapp the files, but should deluge really allocate for the entire close by file?
Example:
- File 1 (1 GB)
- File 2 (1 GB)
If only downloading "File 2" which is 1 GB, deluge allocates for both the files but only downloads maybe 0,58% of "File 1".
This means that for each torrent where I download 1 GB of 2 GB the usage on disk requires it to have 2 GB.
Change History (5)
comment:1 by , 15 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
comment:2 by , 15 years ago
I think you misunderstood, I know you have to download pieces from other files. What my problem is that these files get full allocation.
At least there is the possibility to make an option if you want to do "partial allocation".
comment:3 by , 15 years ago
http://dev.deluge-torrent.org/wiki/Faq#Whatisthedifferencebetweenfullallocationandcompactallocation
Unless you are on windows it's not really an issue, so sorry if you are.
comment:4 by , 15 years ago
I am on Ubuntu, but my external disks have FAT and NTFS for interoperability.
But what you are saying is that the problem would not rise if you partition with EXT?
comment:5 by , 15 years ago
From wikipedia:
"Most modern file systems support sparse files, including most Unix variants and NTFS, but notably not Apple's HFS+."
So as long as you are using your NTFS drive you'll be fine.
http://dev.deluge-torrent.org/wiki/Faq#DelugesometimescreatesfilesthatIdidntaskittodownload.Why