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

[v4.0.x] Notifications and Log file spammed with: An I/O error occurred, ... error: No such file or directory #7992

Closed
hdcTenBasePid opened this Issue Dec 6, 2017 · 9 comments

Comments

Projects
None yet
5 participants
@hdcTenBasePid

hdcTenBasePid commented Dec 6, 2017

qBittorrent version and Operating System

qBitTorrentx64/v4.0.2, Windows 10 Home FCU

What is the problem

When downloading a multi-folder torrent and excluding one or more folders from the download, the Windows 10 Notifications and qBT Execution Log are hit multiple and sometimes continuously with error information as follows (Zzz is a torrent, Yyy a sub-folder, Xxx a file) :
"Date Time - An I/O error occurred, 'Zzz' paused. Zzz partfile read (D:\Torrents\Temp\Zzz\Yyy.unwanted\Xxx.!qB) error: No such file or directory"

"D:\Torrents\Temp" is my 'incomplete torrent' location.

What is the expected behavior

The '.unwanted' file/folder should not be referenced and the error message(s) should not occur.

Steps to reproduce

As per problem definition above.

Extra info(if any)

This appears only to occur after the torrent has begun seeding whilst still downloading.
On a cursory glance may be associated to #7917, #7966.

I Luv your work all.

@SirLT

This comment has been minimized.

Show comment
Hide comment
@SirLT

SirLT Dec 8, 2017

Getting the same error spam with excluded files since updating to 4.0.x 64-bit. Reverting to 3.3.x 64-bit does not fix the problem. Also running Windows 10 Home 64-bit.

SirLT commented Dec 8, 2017

Getting the same error spam with excluded files since updating to 4.0.x 64-bit. Reverting to 3.3.x 64-bit does not fix the problem. Also running Windows 10 Home 64-bit.

@SL-Gundam

This comment has been minimized.

Show comment
Hide comment
@SL-Gundam

SL-Gundam Dec 10, 2017

I'm having the same issue.

I'm using a folder for incomplete downloads which are moved to the default save path after completion
In the incomplete folder i do find a lot of part files like ".24999c72e0bd6fc5526de13122e08b34400addc8.parts"

Could it be those files contain parts of the files that were not selected but had to be downloaded. But the moment the download completes it loses the relation to this file and loses necessary parts?

SL-Gundam commented Dec 10, 2017

I'm having the same issue.

I'm using a folder for incomplete downloads which are moved to the default save path after completion
In the incomplete folder i do find a lot of part files like ".24999c72e0bd6fc5526de13122e08b34400addc8.parts"

Could it be those files contain parts of the files that were not selected but had to be downloaded. But the moment the download completes it loses the relation to this file and loses necessary parts?

@ghost

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Dec 16, 2017

Same problem - it has only happened to me when torrent completed and qb moved the category from wherever I originally had it and moved it to 'seeding' It's almost like it moved the torrent to seeding before it finished checking or hashing or whatever it does to torrent

ghost commented Dec 16, 2017

Same problem - it has only happened to me when torrent completed and qb moved the category from wherever I originally had it and moved it to 'seeding' It's almost like it moved the torrent to seeding before it finished checking or hashing or whatever it does to torrent

@ss7877

This comment has been minimized.

Show comment
Hide comment
@ss7877

ss7877 Dec 29, 2017

Same problem with previous version and 4.0.3.
I found that qbittorrent-3.2.0 does not have this problem.

https://sourceforge.net/projects/qbittorrent/files/qbittorrent-win32/qbittorrent-3.2.0/

ss7877 commented Dec 29, 2017

Same problem with previous version and 4.0.3.
I found that qbittorrent-3.2.0 does not have this problem.

https://sourceforge.net/projects/qbittorrent/files/qbittorrent-win32/qbittorrent-3.2.0/

@fbriere

This comment has been minimized.

Show comment
Hide comment
@fbriere

fbriere Jan 12, 2018

Contributor

I believe this is a duplicate of #7802; see #7802 (comment) for details.

@SL-Gundam: Yup, your analysis was spot on. 😄

Contributor

fbriere commented Jan 12, 2018

I believe this is a duplicate of #7802; see #7802 (comment) for details.

@SL-Gundam: Yup, your analysis was spot on. 😄

@fbriere

This comment has been minimized.

Show comment
Hide comment
@fbriere

fbriere Jan 12, 2018

Contributor

@SirLT: I'm intrigued by your comment, since 3.3 should not exhibit this issue. Although, immediately after downgrading, the torrent will be incomplete at first, since the missing pieces are in a part file which 3.3 would not know how to handle. (But if you let it download, the torrent should complete and remain complete.)

Can you confirm that I am correct, and that your bug is the same as everyone else's?

Contributor

fbriere commented Jan 12, 2018

@SirLT: I'm intrigued by your comment, since 3.3 should not exhibit this issue. Although, immediately after downgrading, the torrent will be incomplete at first, since the missing pieces are in a part file which 3.3 would not know how to handle. (But if you let it download, the torrent should complete and remain complete.)

Can you confirm that I am correct, and that your bug is the same as everyone else's?

@SirLT

This comment has been minimized.

Show comment
Hide comment
@SirLT

SirLT Jan 13, 2018

After deleting the qBittorrent.ini left from 4.0.x, 3.3.16 is working fine. I don't know what's causing the log spam in 4.0 but I haven't tried running it with a clean qBittorrent.ini.

SirLT commented Jan 13, 2018

After deleting the qBittorrent.ini left from 4.0.x, 3.3.16 is working fine. I don't know what's causing the log spam in 4.0 but I haven't tried running it with a clean qBittorrent.ini.

@SL-Gundam

This comment has been minimized.

Show comment
Hide comment
@SL-Gundam

SL-Gundam Feb 17, 2018

Is fixed for me with 4.0.3. Just make sure to force a recheck after upgrading to 4.0.3

SL-Gundam commented Feb 17, 2018

Is fixed for me with 4.0.3. Just make sure to force a recheck after upgrading to 4.0.3

@hdcTenBasePid

This comment has been minimized.

Show comment
Hide comment
@hdcTenBasePid

hdcTenBasePid Feb 18, 2018

I believe that to be true of 4.0.3 and once all previous version outstanding torrents were completed.

However recently, it came up again. This time for real. The reason was corrupt virtual sectors on my SSD.

hdcTenBasePid commented Feb 18, 2018

I believe that to be true of 4.0.3 and once all previous version outstanding torrents were completed.

However recently, it came up again. This time for real. The reason was corrupt virtual sectors on my SSD.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment