New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I/O error: Access denied (Win 8.1 x64, NTFS) #2904
Comments
Tried to limit all connections to minimal values (half-opened, on torrent etc) - no effect. |
As a RAID? |
Can you check the reported system RAM usage while it is close to error out? |
Or set the Disk writh cache size to 1.000 MiB or under and see if the problem persists. |
Sorry for the late response, but I don't now any Russian. |
It's never too late ))) |
Last file is 1,4GB... But what is the total torrent size? |
Checked. The same result. 3.2.0 alpha. |
@arvidn any idea on what to look for here? On what to investigate? |
@arvidn: |
Shmong,do you fix the problem?Can you help Russian student(me) ? =)) |
Since I have a feeling it may be connected, I also get a similar Access Is Denied error (at least, from what I can tell, given it's in Russian). Appears to only occur with torrents I transferred over from uTorrent back when I switched, although within uTorrent they were completed with no errors. I tried poking here and there to see if I could figure out what may be the issue, but it appears random (only a few of the ones transferred from uTorrent, and all are located within the same external drive as the ones that don't send errors). I tested moving the affected file (as it's only ever one or two within a torrent, not every file) to another folder and letting it redownload, which worked for one torrent that was throwing errors; it redownloaded the affected file successfully - although another file within that torrent began throwing errors. I eventually managed to get that torrent to Completed by repeating that process, however redownloading has not worked for any other downloads. The torrents themselves will get seeds and begin downloading, but will only go up a few KiB and then spring the error, and slowly work their way down to nothing (although sometimes they just sit around a few KiB for hours before doing so, while still springing the error and seemingly not downloading anything, despite changing my Downloaded amount) before stalling out. I would post my RAM usage, but my computer is terrible so most of my usage stats are close to max at all times; despite this torrents can upload and download fine, with the exception of the few afflicted torrents. If this is unrelated to this open issue I can move it to its' own issue. |
Bump. I've been googling for hours on this problem to find this issue. I get the impression this is not a widespread problem and thus not pressing enough issue. It still means I cannot use qBittorrent, sadly. Running as admin, I get the error when adding previously unselected files to be downloaded from the torrent. The download location is set to an external USB drive. After the error, I have to force re-check to make it work again. But I cannot add any files. Have there been any ideas on this in the past couple of years? Thanks |
Is there a way in qbt to "clear error" on a torrent? I would expect stopping and starting again would do that, but perhaps it doesn't. My suspicion is that your disk error happens for some reason. the torrent is stopped with an error. In order to resume the torrent, the error has to be cleared (by calling If starting the torrent would also clear the error first, at least you could just do that instead. However, the underlying disk error is a different question. To have a chance of understanding that, we would need more information from the error message in the log. |
@glassez ping, what do you say about this? |
Only the following for the start:
|
I've since had to move to another client as because of this issue I cannot use qbitorrent. Thus also not able to provide a log very conveniently, sorry. If you show me how to easily generate a log I can look into this again. |
@Richard-L if on windows, logs are found here -> |
@glassez here's a possible example of the error:
This was from setting 3 torrents to my main |
@xavier2k6 thank you, I have the log now. How can I send this to someone privately? |
@Richard-L it would be better to just censor/redact the parts you find sensitive and post here. |
@FranciscoPombal okay, I have added some ######. I hope it's still useful. Is it possible the problem stems from when people "rename" the torrent since they want their own name of the destination sub-folder? I had done that in the "add torrent" dialogue. The name I'd chosen is unedited in the log. |
it looks like the call to |
Or, could the path be too big (in case you haven't lifted the |
@arvidn @FranciscoPombal thank you for your assistance. I've done some tests and the problem only occurs if I use the "rename" function available when adding torrents. If I leave the folder name provided by the torrent itself, it all works fine. Can you reproduce this error? |
Can you provide complete "steps to reproduce"? |
I can reproduce but rename is irrelevant for me and at step 6:
On a usb flash drive i get the same error Official 4.2.5 |
Oh no..... Guess I'll have to not use the rename feature then, although his will create quite a bit of room for error in my case. |
Couldn't reproduce it on windows 10 with qBt 4.2.5 as well as latest master. |
I'll repeat my question:
IIRC the restriction can only be lifted in Windows 10 version >= 1607. But to be honest, even if the problem is something else, you shouldn't be using Windows 7 at this point, it has been EOL for nearly half a year already. |
@FranciscoPombal Win7 is still officially supported by qBittorrent, right? Win10 deleted my %userprofile% files after a WindowsUpdate several times and I lost too much important data because of it. I did have the long path restriction fix checkbox ticked when installing both times, but as you say this is only available on Win10. I assume you mean that option? While I don't think my desired path is overly long, indeed I cannot reproduce the problem with a shorter path closer to root level. Is this path fix possible for Win7? |
Only in the sense that "its dependencies still happen to work on Windows 7, for now". Windows 7 is EOL and has received no security updates for nearly half a year. Additionally, no developer/contributor (that I know of, at least) is running Windows 7 and testing on it. Furthermore, unexpected problems may arise from
True, there was one well-documented case of a Windows Update that deleted some users' data. Solutions for stuff like this are:
Yes.
"I don't think my desired path is overly long" is not precise enough. It's either too long or it isn't. The standard path length limit in Windows is 260 characters, including the invisible terminating From what you describe, the problem does seem to be too long file paths.
No. At least not on qBittorrent's side. Honestly, just move to a non-obsolete OS. |
Hello, An Example -
|
I would expect long file names not to be the only reason to get this error (and names are supposed to be truncated as well). Perhaps there's a character encoding issue in the file names, or some other invalid character in it. |
All the characters are in English and there are usually 2-3 pairs of round brackets in the name. All the affected file names were between 25-50 characters long with the folder name being the same. I download them 1 level below the main directory with the folder name being 5 characters long. So the an example of the final path would be- |
Do they have the uTorrent extension attached to them, is uTorrent closed? etc. |
Well, brackets are forbidden in NTFS filenames. |
I assume by "round brackets" they meant "parenthesis" ( @mishrasumitranjan @Richard-L please post example torrents/hashes that can be used to reproduce the problem. |
|
@xavier2k6 They were completed files. No partial data or uTorrent extension remaining. uTorrent was also closed at the time. Since I thought that might be what is causing the issue. @glassez I meant 'Parenthesis'. Angle brackets were a way to say 'put anything 25-50 characters long here'. @FranciscoPombal Here is a zip containing two files. The one numbered 3 is the older. The one numbered 4 is an update and contains one file more. |
Well, the paths are not especially long and they definitely don't contain any weird characters, not even characters NTFS on Windows disallows, so that is not the problem. Can you reproduce the problem when not using an external drive? Can you reproduce it using any (sample size of 2 is acceptable here) external drive? |
@FranciscoPombal |
I've had no problem with these torrents when doing the following:
It should also be no problem doing step 1 with a different client other than qBittorrent, but in this case the torrent should be removed from the other client and that client closed before doing step 2. There's probably something wrong with your system, permission-wise. |
New torrents and torrents previously downloaded with qBittorrent do not have any issues downloading. |
So the issue only happens when uTorrent is also running? If so, I don't think there is anything we can do. |
@FranciscoPombal Yes, I think so. |
Alright, issue appears to be due to uTorrent interfering, so this is not an issue with qBittorrent. In #2904 (comment), we can also see that uTorrent is running in the background, so most likely OPs problem is the same. Thus, we can consider this solved. There is an unrelated reproducible issue mentioned in #2904 (comment) - @thalieht can you still reproduce? If so, I'll close this one and open a new ticket to focus on that specific issue. |
Latest qBt version is still 4.2.5 and since i mentioned the problem involves the .unwanted folder for me, i have no reason to try to reproduce. Just assume it still happens (for me). |
Wasn't the |
Yes it was @thalieht Hopefully, you'll be able to confirm with below?! Windows test build of 4.3.0(Alpha1) with listed libraries:
|
Thanks @xavier2k6. I don't get I/O errors with this build. /Offtopic
|
Alright, looks like everything is resolved then. Thanks! |
I have an error when downloading new torrent over current one, like TV-series.
I've started the new download, after deleting previous one, started with administrator priveleges, etc etc... but each time i see the error after hash-check.
qBitTorrent checking pre-last file on ~97-99% then start check in the last file (it's not completely downloaded before by qBit) and then i see an error.
If i using uTorrent instead - everything be OK. I've reinstalled the system from Server 2012 (it has the same error). HDD is not the reaso, cause uTorrent is allright and i've checked all of them (actually i'ts 3 different HDD)
The text was updated successfully, but these errors were encountered: