qBittorrent 5.0 error when trying to save a torrent on a network location (NAS). It cannot create folders.

[sppmasterspp]

qBittorrent & operating system versions

qBittorrent: 5.0.0 x64 Operating system: Windows 11 Pro x64 (23H2) 22631.4317 - I've tried it on two different PCs. But it does work on Debian. Qt: 6.8.0 Libtorrent: 2.0.10.0 Boost: 1.86.0 OpenSSL: 3.3.2 zlib: 1.3.1 Found Python executable. Name: . Version: "3.9.13"

What is the problem?

When I open a torrent file and choose a network location to save it, qbittorrent gives an error. This happens when a new directory for the torrent should be created. I get - "Parameter error" and qbittorrent is unable to make a directory for the torrent, If I choose qbittoreent not to create a directory then all torrent files are written properly to the NAS SSD. Or if I create the directory manually before adding the torrent file then the torrent files writing to disk is OK. The program creates a file without any extension with an unrecognized empty icon under Windows File Explorer. When I choose to remove the torrent and data from the qbittorrent the file is not removed and remains on the NAS drive. All of this started with version 5.0.0 and current alpha 5.1.0. Before that everything was OK. In my case I have a SSD USB3 (formatted with F2FS file system) attached to my OpenWrt router and I use it as a NAS device. Everything else works OK with this setup. I have automated backups on that NAS drive. Using other torrent clients like uTorrent with the same torrent files results in successful operation. Screenshots below.

Steps to reproduce

Steps to reproduce are like opening any other torrent the usual way but choose to create folder for the torrent. I cannot tell if the F2FS file system have any impact here because I tried to save the same torrent to another shared network folder on a Windows 11 PC and it was OK. But this issue was not present with older qbittorrent versions. I know that this may be somewhat unusual setup (F2FS mostly) and maybe because of this the issue went unnoticed. I suppose (my speculation here) that the issue maybe caused by recent commits introduced with the kernel 6.6.54. https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.54 There are lots of F2FS related commits there. And probably qbittorrent has some issues with those commits too.

Additional context

Log(s) & preferences file(s)

22.10.2024 г. 16:57 - File error alert. Torrent: "xxxxxxxxxxxxxxxxxxx". File: "\qnap\qnap-usb1\". Reason: " error: The parameter is incorrect"

[stalkerok]

When I choose to remove the torrent and data from the qbittorrent the file is not removed and remains on the NAS drive.

Duplicate of https://github.com/qbittorrent/qBittorrent/issues/21245

The I/O error is not a qBittorrent error, but a device error. qBittorrent simply cannot write data to it.

[sppmasterspp]

The I/O error is not a qBittorrent error, but a device error. qBittorrent simply cannot write data to it.

I don't agree it's a duplicate. How isn't that a qbittorrent error when every other software writes and creates folders/directories to the same drive from several PCs without any issue. And how the old version didn't have this issue. Qbittorrent writes the data but cannot create folders/directories. Hence the next error it is unable to write there. The directory doesn't exist.

[stalkerok]

I don't agree it's a duplicate.

You have multiple issues here in one issue, one issue is a duplicate.

but cannot create folders/directories. Hence the next error it is unable to write there. The directory doesn't exist.

Are you sure qBittorrent has all the necessary write permissions? Also try disabling “Mark-of-the-Web (MOTW)” in advanced settings.

[sppmasterspp]

Are you sure qBittorrent has all the necessary write permissions? Also try disabling “Mark-of-the-Web (MOTW)” in advanced settings.

It writes if I choose it not to create folder and disabling above option doesn't change anything. It cannot create folders.

[qBittUser]

Libtorrent: 2.0.10.0

Try qBittorrent with v1.2.19+ (RC1_2), it should have less issues with external drives.

... current alpha 5.0.1

Currently there's no such version of qBittorrent.

Latest alpha nightly builds in GitHub from master branch are v5.1.0alpha1, not v5.0.1 and if you're using qBittorrent with code from v5_0_x branch, then it doesn't include all upcoming fixes yet, because currently everything planned to be backported hasn't been merged into v5_0_x yet.

[sppmasterspp]

GitHub from master branch are v5.1.0alpha1, not v5.0.1

It's my mistake I've updated to alpha 5.1.0 just to see if the 5.0.0 error will pop out with it too.

[sppmasterspp]

Try qBittorrent with v1.2.19+ (RC1_2), it should have less issues with external drives.

Same error with 1.2.19. Additionally when I try to open the torrent destination folder from the qbittorrent right-click menu I get this. It simply tries to open the unrecognized file (actually this is the name of the folder that qbittorrent should create but it fails to do so).

[qBittUser]

@sppmasterspp

Unfortunately different OS and file systems support or don't support certain file or folder names and torrenting clients don't always silently and automatically fix incompatibility issues.

Try re-adding torrent or pause and then rename folder to something more common, otherwise your OS, File manager or Virus protection software thinks it's a file with unknown file extension, not a folder name.

[stalkerok]

@sppmasterspp Can you give me an example of such a torrent?

[sppmasterspp]

Can you give me an example of such a torrent?

I'm not sure because for me it faults with every torrent that needs a folder creation on my NAS network drive. I've just tried another one with more common name but it failed again. If i create the same folder name manually before starting the torrent, then it finishes without error. The interesting part is that other software applications can create folders OK.

[stalkerok]

hash please if it's not a private torrent.

[sppmasterspp]

hash please if it's not a private torrent.

Infohash : B8D6CA8C95B3735C5CB21E9F5147DCDD8F155333

[qBittUser]

@sppmasterspp

I would try downloading Ubuntu ISO file using *.torrent into NAS, then everyone can be 100% sure there's no obvious reason not to be able to download or move existing files with qBittorrent.

https://ubuntu.com/download/alternative-downloads

If it fails, then exit qBittorrent and try downloading or preallocating and moving files with other torrenting clients to know if torrenting clients using libtorrent or something else is causing issues.

[stalkerok]

Infohash : B8D6CA8C95B3735C5CB21E9F5147DCDD8F155333

No issues, either with this or with Technotronic - Pump Up the Jam [1989] WavPack a62f753b40cbfac61cf8757efdcc000d3bc35cc7

@xavier2k6 @glassez take a look, please. Perhaps the issue is really in libtorrent.

[xavier2k6]

In my case I have a SSD USB3 (formatted with F2FS file system) attached to my OpenWrt router and I use it as a NAS device.

It may be to do with file system in-use. (have no way to test this setup)

[sppmasterspp]

It may be to do with file system in-use. (have no way to test this setup)

Guys, thanks a lot for your help looking into this. I know that this may be somewhat unusual setup (F2FS mostly) and maybe because of this the issue went unnoticed. I suppose (my speculation here) that the issue maybe caused by recent commits introduced with the kernel 6.6.54. https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.54 There are lots of F2FS related commits there. And probably qbittorrent has some issues with those commits too. Unfortunately it is difficult for me to go back to the previous kernel 6.6.53 as I'm currently on 6.6.57 but I haven't used the qbittorrent for some time and cannot be absolutely sure about that exact kernel version but it looks suspicious with those F2FS commits. I know for sure that a month ago I didn't have this folder creation issue. I installed older bittorrent version that I remember worked OK but now it has the same issue so I suppose it's indeed related to any F2FS recent commits. I hope so. Please check the ChangeLog-6.6.54 maybe that will help resolve this.

To summarize the current issue.

qBittorrent cannot create folders when I open any torrent (including below one Ubuntu ISO) and choose it to create folder (or keep the original torrent structure that includes a folder). I see the Parameter error in this case. If I deliberately choose not to create a folder the files are downloaded without any issue.

I would try downloading Ubuntu ISO file using *.torrent into NAS, then everyone can be 100% sure there's no obvious reason not to be able to download or move existing files with qBittorrent.

Other programs like GoodSync, uTorrent, File Explorer, WinRAR, Total Commander can create/delete folders on the same F2FS formatted NAS drive. At the moment I workaround this issue by manually creating the folder on the NAS drive (using the exact torrent folder name from the torrent info hash) before starting the torrent downloading. Do you have any other suggestions what else I can try in order to help resolve this. Any debug options to run? If there is no other way I will try to return to a build before the kernel 6.6.54 but that may take some time because my local network is really busy during the daytime with lots of services, VPN, etc. It's reproducible on two different Windows 11 PCs. Last minute update - I've installed 5.0.0 on Debian and it's working completely OK. Creates folders too. Regards.

[HanabishiRecca]

You never mentioned what kind of network share drive you use. SMB? NFS?

I know that this may be somewhat unusual setup (F2FS mostly) and maybe because of this the issue went unnoticed.

I don't think it matters. Because network drives have no idea about the physical filesystem on the other side. And The parameter is incorrect is a Windows error.

[sppmasterspp]

You never mentioned what kind of network share drive you use. SMB? NFS?

I use SMB - ksmbd. I've found and reported KSMBD errors in the past but the version hasn't changed for a few months. I first thought that it was KSMBD issue again but version is the same and it worked OK since the reported issue was resolved.

I don't think it matters. Because network drives have no idea about the physical filesystem on the other side. And The parameter is incorrect is a Windows error.

Maybe not entirely true (I think as you think but then why all those F2FS commits were pushed). It maybe a Windows specific error but then why other programs can create folders on the NAS?

[HanabishiRecca]

Anyway, qBittorrent does not create the directory in this case. Libtorrent does. https://github.com/arvidn/libtorrent/blob/24e658aa884cb91bb9918487ba0e9bb51d7bf70f/src/path.cpp#L381

CreateDirectoryW is a WinAPI call. How it possibly could fail? No idea.

[sppmasterspp]

Anyway, qBittorrent does not create the directory in this case. Libtorrent does. https://github.com/arvidn/libtorrent/blob/24e658aa884cb91bb9918487ba0e9bb51d7bf70f/src/path.cpp#L381

So maybe I should create issue on @arvidn libtorrent github.

[HanabishiRecca]

Probably yes. Arvid could dig deeper into it.