Torrent Errors: Operation Not Supported

[anubeon]

Greetings All!

I'm having some issues with deluge, to be more specific I am receiving no descriptive torrent errors referenced under the details tab as "Status: Operation not supported". I have a dual boot set-up whereby I've configured both uTorrent (Windows) and Deluge (Ubuntu) to use the incoming, torrent and auto-load folders.

One my torrents seems to be impervious to this error, at least so far. The others, those effected by this error, typically download for a while after manual resumption only to report the same error after a few minutes. I've attached a couple of screenshots for your perusal, the first is of the seemingly impervious torrent (the one that's behaving itself) and one of one of the erroneous torrents.

Impervious Torrent


Erroneous Torrent


It may be worth noting that I have removed and re-downloaded the torrent files (leaving the data in place) several times and that I have had to do this for all of the torrents, including the one that is operational, each time I boot out of Windows and into Ubuntu. I suspect that running uTorrent and Deluge out of the same folder set isn't workable, but if there is any way to get it working it would be preferable to the alternative (since I spend a significant amount of time in both operating systems).

I would be greatly appreciative of any assistance provided. I would also prefer a more verbose assessment of the error(s) at hand; "Operation not supported" isn't much of a handle for troubleshooting!

Regards,

Anubeon

P.S. I should probably point out that I've set out port forwarding within both Linux and my router and as far as I can see ports are being forwarded successfully.

[anubeon]

Really, nobody here has any idea what could be causing this? This non-descriptive error is rather frustrating, so I'm going to run deluge with logging (I'll start with error logging, as I think critical and debug logging would be overkill for this issue. I'll dump the log here as a .txt attachment and hopefully some kind person will have a better idea as to what on earth is wrong.

Please Help Me!

[Cas]

you have not mentioned what version you are running and there have been three releases since your post so it may have been assumed to be resolved. have you tried the newer versions?

attaching logs is most useful

[anubeon]

Thank you for responding to my recent plea for help.

As it happens the original incident, back in February, seeming to fix itself. The error messages continues for about a week after I made my original post and then everything just worked. I have no idea what if anything I did that might have rectified the situation and I'm fairly certain that this occurrence did not coincide with a update to Deluge. In any case, two days ago I started to receive the same error messages and behaviour as before (i.e. torrents connected long enough to retrieve a peer list in the thousands, downloaded for a minute or two and then paused with the previously described error message of 'operation not supported'). Of note is the fact that this error effects new torrents ONLY; pre-existing torrents for which I am seeding (and no longer leeching) are working fine and in some cases use the same trackers as the new torrents that have failed. Also worthy of note is the fact that I am currently running Deluge 1.2.2 under Ubuntu Lucid Lynx (beta), as opposed to Deluge 1.2.0 under Ubuntu Karmic Koala (release) back in February.

The last time this happened in February it effected only Deluge, which at the time was the only torrent client I had installed on Ubuntu. The same torrents that were throwing up error in Deluge/Ubuntu were working just fine in uTorrent/Windows 7. This suggests to me that the issue resided at programme (Deluge) or system (Ubuntu) level, and was not an issue with the tracker(s) and/or router configuration. Unfortunately, due to a recent upgrade of grub my Windows 7 partition is inaccessible and so I cannot confirm whether or not uTorrent is effected at this time. I can however confirm that the very same error is reported within Transmission in Ubuntu, and that I have observed similar behaviour (i.e. connection long enough to retrieve peer list and download for a minute or two before the error rears its ugly head) in Transmission. I realise of course that by opting to test a pre-release operating system I have complicated matters, but hopefully the attached log file (which I can make neither head nor tails of) may shed some light on what is the cause of this behaviour and at the very least guide me in deciding if and where to report a bug and make further inquiries.

Lee.

P.S.: Also, I do apologise if I came off as rude and generally 'snarky'. I was simply vexed that after nearly three months this thread hadn't received so much as a "hello" or even a "s*d off".

[Cas]

"Operation not Supported" is a libtorrent error relating to the filesystem as you probably suspected.

From docs:

If the storage fails to read or write files that it needs access to, this alert is generated and the torrent is paused.

I cannot answer why it is occurring but it would be useful to know what filesystem you are using for active torrent storage.

There are a lot of improvements in libtorrent 0.15 regarding the filesystem, so there is an option for you to build Deluge 1.2.3 with libtorrent 0.15 from source code.

P.S.: Also, I do apologise if I came off as rude and generally 'snarky'. I was simply vexed that after nearly three months this thread hadn't received so much as a "hello" or even a "s*d off".

Not at all, if its any consolation, welcome back to the forum
Most likely the post got overlooked or forgotten to be checked as there are only a few active deluge devs, also I would say that after a week or two it is ignored for the reason I explained previously.
I will try to answer questions but usually without any answer to provide I leave them to someone more qualified but since I have been given the role of moderator I will attempt to give some form of response if posts go unanswered.

[anubeon]

I cannot answer why it is occurring but it would be useful to know what filesystem you are using for active torrent storage.

Torrents are downloaded to an NTFS share, this has been the case since I installed my dual boot system in January so I cannot see that being the cause. Although you'd probably be a better judge of that than I.

There are a lot of improvements in libtorrent 0.15 regarding the filesystem, so there is an option for you to build Deluge 1.2.3 with libtorrent 0.15 from source code.

I might just do that, although I am curious as to when Deluge 1.2.3 (and libtorrent 0.15) will be made available via the Deluge Team PPA. If it's a matter of days (or even hours) I can wait.

[Cas]

Torrents are downloaded to an NTFS share, this has been the case since I installed my dual boot system in January so I cannot see that being the cause. Although you'd probably be a better judge of that than I.

I would say that this is a possible cause of your issues. If you dont need windows anymore i would really suggest moving to ext4 and there is actually a ext driver for windows that works quite well if you need access to ubuntu files..
The other option i suggest to try in the meantime is to setup a ext4 partition (10-20gig) where you save the torrents then use Move Completed setting to move them to the NTFS drive.

I might just do that, although I am curious as to when Deluge 1.2.3 (and libtorrent 0.15) will be made available via the Deluge Team PPA. If it's a matter of days (or even hours) I can wait.

No idea I'm afraid, it can take a few weeks to appear.

[anubeon]

I would say that this [NTFS] is a possible cause of your issues.

It would appear so, although it didn't seem to cause me any problems for over a month. How odd!

If you dont need windows anymore i would really suggest moving to ext4 and there is actually a ext driver for windows that works quite well if you need access to ubuntu files..

I already have a 4GB /home partition formatted ext4, I think I could get by downloading torrents their and moving completed torrents to my NTFS storage partition. In the long run I think I may need to expand my /home partition to 10-20GB though. Also as far as I am aware there is no Windows driver available that will work in a stable way with ext4. I recall stumbling across one for ext2 that is reported to work, at a much diminished capacity with ext3 partitions, but that's about it. Of course if you know different I'd appreciate an URL! Note though that I am running Windows 7 Profession x64, any driver would (presumably) need to be 64-bit compatible.

No idea I'm afraid, it can take a few weeks to appear.

Oh well, now the issue is resolved it's I'm not desperate to upgrade. I can wait for the repositories to be updates with the 1.2.3.

[Cas]

Also as far as I am aware there is no Windows driver available that will work in a stable way with ext4.

I have used ext2fsd and have not had any troubles. There is a caveat for ext4 that you need to have disabled extents when formatting the ext4 partition.

There is a good guide here:
http://www.soluvas.com/read-browse-expl ... windows-7/