qBittorrent
qBittorrent copied to clipboard
.ISO files downloaded with qBit can't be mounted with Windows 8~8.1 native function.
When downloading a .ISO file with qBittorrent the ISO file is never able to be mounted by Windows 8~8.1 (Error: Couldn't Mount File: Sorry there was a problem mounting the file.)
Closing qBit doesn't solve. Restarting PC doesn't solve. Renaming ISO doesn't solve. Cuting the ISO to other place doesn't solve. ISO file is forever that way unless you copy and paste it to other place in your harddrivre.
Doesn't happen in uTorrent.
Sorry if it is not the right way to report an issue, it's just that this is a bug that I and friends have and I haven't seen it reported.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
ISO file is forever that way unless you copy and paste it to other place in your harddrivre.
Then it is more likely to be permissions on the download location. If it was anything to do with qBT directly ... moving the file would have no effect whatsoever.
Copy and Pasting it in the same folder that it has been downloaded works...
I don't know what is happening here, but we don't touch file permissions. Can you check the file attributes before and after you copy it? Are you using v3.1.12?
Using v3.1.12, in the Windows Explorer details page there's a difference in attributes with the original having "AP" and the copy having only "A".
If I can use any other software to help you guys just say it.
the 'P' Attribute indicates a 'sparse' file, does the same happen with a Linux distro iso?
http://torrents.linuxmint.com/torrents/linuxmint-17.1-kde-32bit.iso.torrent
Yeah, all the same.
This is libtorrent's problem, it was supposedly fixed already. It should have removed that attribute upon completion. Can you try with the v3.2.0beta which uses libtorrent 1.0.x instead of 0.16.x? Link: http://qbforums.shiki.hu/index.php/topic,3310.msg16116.html#msg16116
Still happens in v3.2.0...
Does qBit needs Administrator rights to remove the attribute?
I opened this: https://code.google.com/p/libtorrent/issues/detail?id=736
Still happening. This is extremely annoying, and imo a huge problem.
@sledgehammer999 how is this issue?
Fixed in Windows 10, file still AP upon completion but Windows can now mount it regardless.
@ngosang I haven't investigated. The issue is that libtorrent doesn't remove the "sparse" flag from the file upon its completion. See the libtorrent bug I linked to if you want to troubleshoot.
I don't know if @arvidn is working on it, if not we can hack it. IMHO this should be fixed asap.
in file::close
(file.cpp in RC_1_0 branch) there is a condition like this::
if ((rw_mode != read_only)
&& (m_open_mode & sparse)
&& !is_sparse(m_file_handle, use_overlapped))
It is expected that when a file has completed downloading and is closed, this condition will be true and the code in this block is executed. The code under this condition will un-set the sparse flag of the file.
For someone on windows, it would be very useful to find out why this code wouldn't be run. Presumably one of those three conditions is false. My guess is that it's most likely the last one, but possible the middle one, that are failing. The is_sparse()
check makes sure the file is actually completely downloaded. It doesn't check for whether the sparse flag is set or not, it checks to see if there are any actual holes in what's stored on disk. If there isn't, we might as well just uncheck the sparse flag. A file that's completely downloaded is not expected to have any holes in it.
This is definitely very annoying, and happening me on Windows 10.
I have an XPS 15 (for programming) and an Inspiron 15 7000 (for gaming) - Both have SSDs as their main drives, which is where qBittorrent is saving.
On my XPS 15, .isos are no problem, while on the Inspiron, every iso I've downloaded has had the sparse flag set, requiring me to run fsutil sparse setflag "path" 0
.
After running that command the isos work no problem - the downloads are definitely completed.
I'm not set up to test & track down where the problem is, but it's honestly massively annoying. This has been happening since I installed qBittorrent on my Inspiron (which was basically 5 minutes after I got it half a year ago).
The current version I'm running is v3.3.15 on both computers.
Is this still relevant ?
@arvidn, just checking if this (https://github.com/qbittorrent/qBittorrent/issues/2854#issuecomment-133945211) is still relevant?
Closing. This is libtorrent related and by the looks of it and activity - obsolete.