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
After updating from 4.6.3 (2.0.9) to 4.6.3 (2.0.10) or 4.6.4 (2.0.10), all completed tasks disappeared. #20772
Comments
It would be more interesting to see the differences of Qt between these two builds. I believe the current one causes the problem. @Chocobo1 |
I just tried upgrading from 4.6.3 (2.0.9) to same binary 4.6.3 (with lib 2.0.10), and the same errors show up in the log file. So I am pretty sure, it is Lib 2.0.10 and not the main binary. For some reason, Lib 2.0.10 fails to read categories.json and all the fastresume files, same for 4.6.3 and 4.6.4 |
This error is not produced by qBittorrent/src/base/utils/io.cpp Lines 78 to 92 in 769de08
And But if you still insist, I won't stop you from dealing with this problem as you know. |
I do see your point, but 4.6.3 (2.0.9) produces no error, however same 4.6.3 (with 2.0.10) produces all the errors. That's how I deduced my result. Do you have any theories on why only changing the lib leads to these errors? What you have given is the function that prints this error, but who is calling this function() ? It is like you see a knife with blood, but who is using the knife? |
Cross checking all the components for QT6, the only change in the nox is Libtorrent https://github.com/userdocs/qbittorrent-nox-static/releases/tag/release-4.6.3_v2.0.9 |
@ivan-yu |
I'm not setting a filesize limit.
Unless that issue is specific to Qt 6.7.0 since I will assume this is the error path
Which will be Qt 6.6.2 to 6.7.0 I'd consider that an upstream issue as I just build the app, my build is not causing the issue it would be exposing the it, |
I didn't say that you set any limit. It's just that one of your builds behaves incorrectly.
Nothing that could cause this problem has changed in the qBittorrent code between version 4.6.3 and 4.6.4 (even up to the current master). |
Please see below two log files.
|
You can see all the file open function calls failed. They all say File size: 547866034680 547866034680 is obviously not the file size at all. For example, categories.json is just 4 bytes in size. -rw-r--r-- 1 root root 4 Mar 23 20:52 categories.json |
May I suggest you create a path the same as mine, to replicate this file open error? |
Closing this issue since it seems to be more a build issue, following up with the builder. |
It seems the root cause is statx() failing, when trying to get file size. statx() seems to only exist from Linux Kernel 4.11 If anyone is running earlier version (e.g. Linux Kernel 4.9), this call will fail |
Due to my limited Linux knowledge, I cannot tell whether this issue is within the source, or due to how the aarch64 binaries are built by the builder. strace of non daemon qbittorrent
|
Your strace shows that |
RIght, the statx() call returned non sense file size (stx_size=549135500224). Then QT treats this size as failure when compared to a user defined file limit. Finally, file open fails with QT, for all files including fastresume files. As a result, all completed torrents cannot be recovered. However, I do not understand why QT4.6.3-LT2.0.9 does not have any issue. Does LT 2.0.9 also use statx()? Or does it use older stat()? My NAS (Linux environment) has not changed.
|
I think the root cause has been identified.
The fallback did not work |
@glassez if you are interested in what is the cause of this is should it crop up again. |
qBittorrent & operating system versions
qBittorrent: 4.6.4 aarch64
Operating system: Linux version 4.9.119
Qt: 6
libtorrent-rasterbar: 2.0.10
What is the problem?
I found below errors inside log file, after I update from 4.6.3 (2.0.9) to 4.6.4 (2.0.10)
My categories.json is just 4 bytes, not what the log file says.
Steps to reproduce
No response
Additional context
No response
Log(s) & preferences file(s)
No response
The text was updated successfully, but these errors were encountered: