Jump to content

uTorrent 3.3 (build 29544) [32-bit]: Incorrect function (WriteToDisk)


Radish

Recommended Posts

I previously posted this in the "Troubleshooting" section. under the thread title - "Multiple Errors: Incorrect function (WriteToDisk)" I am now posting this to "Bug Reports" because I am now pretty well convinced that the problem is being generated by a bug. Problem is as follows (and this is duplicate information from "Troubleshooting"):

O.S. WinXP Pro Service Pack 3 [32-bit]

uTorrent 3.3 (build 29544) [32-bit]

Hi,

I just downloaded UT 3.3 yesterday and have been using it for a day and a bit now. I keep getting multiple errors 'Incorrect function (WriteToDisk). When I get the error UT stops activity for the relevant file. Then I have to force a recheck and then re-start the torrent. I'm wondering if UT 3.3 has changed the way it writes to disk? Or maybe there is another explanation that I'm not aware of. Any ideas? Just in case it is important - I do get UT to pre-allocate download files.

A representative portion of the log is as follows:

[2013-04-23 21:16:40] IO Error:1 line:920 pos:1083177378 count:1048576 actual:-99

[2013-04-23 21:16:40] Error: WhyInTheWorldAreTheySpraying - Incorrect function. (WriteToDisk)

[2013-04-23 21:16:40] IO Error:1 line:920 pos:817133986 count:638976 actual:-99

[2013-04-23 21:17:14] IO Error:1 line:920 pos:1129996325 count:2097152 actual:-99

[2013-04-23 21:17:14] Error: China Syndrome - Incorrect function. (WriteToDisk)

[2013-04-23 21:18:12] IO Error:1 line:920 pos:832200741 count:2097152 actual:-99

[2013-04-23 21:18:12] Error: China Syndrome - Incorrect function. (WriteToDisk)

[2013-04-23 21:24:14] DNS resolution failed for tracker udp://inferno.demonoid.com:3416/announce

[2013-04-23 21:41:46] IO Error:1 line:920 pos:1461346341 count:2097152 actual:-99

[2013-04-23 21:41:46] Error: China Syndrome - Incorrect function. (WriteToDisk)

[2013-04-23 21:48:08] IO Error:1 line:920 pos:1373265957 count:2097152 actual:-99

[2013-04-23 21:48:08] Error: China Syndrome - Incorrect function. (WriteToDisk)

[2013-04-23 21:48:08] IO Error:1 line:920 pos:278552613 count:2031616 actual:-99

[2013-04-23 21:49:50] IO Error:1 line:920 pos:748314661 count:2097152 actual:-99

[2013-04-23 21:49:50] Error: China Syndrome - Incorrect function. (WriteToDisk)

[2013-04-23 21:56:48] IO Error:1 line:920 pos:104488997 count:1916928 actual:-99

[2013-04-23 21:56:48] Error: China Syndrome - Incorrect function. (WriteToDisk)

[2013-04-23 21:56:48] IO Error:1 line:920 pos:599416869 count:786432 actual:-99

[2013-04-23 21:56:48] IO Error:1 line:920 pos:1228562469 count:1261568 actual:-99

[2013-04-23 21:58:32] IO Error:1 line:920 pos:693788709 count:2097152 actual:-99

[2013-04-23 21:58:32] Error: China Syndrome - Incorrect function. (WriteToDisk)

[2013-04-23 22:03:59] IO Error:1 line:920 pos:538599461 count:2097152 actual:-99

[2013-04-23 22:03:59] Error: China Syndrome - Incorrect function. (WriteToDisk)

[2013-04-23 22:04:00] IO Error:1 line:920 pos:664428581 count:1327104 actual:-99

[2013-04-23 22:04:00] IO Error:1 line:920 pos:146432037 count:1458176 actual:-99

[2013-04-23 22:05:38] IO Error:1 line:920 pos:1467637797 count:1949696 actual:-99

[2013-04-23 22:05:38] Error: China Syndrome - Incorrect function. (WriteToDisk)

[2013-04-23 22:05:38] IO Error:1 line:920 pos:1366974501 count:688128 actual:-99

I should add that this isn't restricted to a single torrent - this is happening with every torrent I try to download.

============= Duplicate Information Ends Here =================

I had one response to that post from ciaobaby suggesting that the 'Incorrect function' "Usually indicates that the location is read only."

I checked this today and none of the torrent files being downloaded are shown by my system as being 'read only' (and why should they be).

Okay, so today I started a new torrent using uTorrent 3.3 (build 29544) [32-bit] - same version and build that was generating the above errors.. Within a few minutes I was back with multiple errors as detailed above. In the end I just gave up on the torrent with this 3.3 version of uTorrent.

Okay, so I installed uTorrent 3.1 (build 26650) - I had a copy on my hard-drive - and tried downloading the same torrent using that version 3.1 of uTorrent. Result of this experiment was that the torrent downloaded flawlessly. (Note that before installing uTorrent 3.3 I had been using uTorrent 3.2 and that had been downloading flawlessly too - I just didn't have a copy of it on disk to experiment with as my install of 3.3 overwrote my 3.2 before I remembered to copy it out of the install folder.)

My conclusion from this is that uTorrent 3.3 (build 29544) [32-bit] definitely has a bug concerning writing of data to hard-drive. Again I need to ask the question has uTorrent 3.3 (build 29544) in any way had the way in which it writes to disk changed? If this is the case then you have added a bug into the new code.

In light of my experiment I can't think of any other reasonable explanation.

Link to comment
Share on other sites

Thanks for the response rafi,

No I haven't tried any beta version and I really don't think I want to as I'm no expert on p2p, I'll just get stuck if anything untowards happens.

I just found a copy of uTorrent 3.2.3-28705 on my backup drive so I'll use that for now, that wasn't showing up this problem either.

Once a new, higher, stable version is out I'll give that try.

Many thanks.

Link to comment
Share on other sites

I had one response to that post from ciaobaby suggesting that the 'Incorrect function' "Usually indicates that the location is read only."

I checked this today and none of the torrent files being downloaded are shown by my system as being 'read only' (and why should they be).

It is NOT the files that are 'read only" but the drive or the path.

For example trying to write to C: rather than C:\ would result in an "Incorrect function" as would writing to a CD or DVD drive.

Link to comment
Share on other sites

Hello Ciaobaby,

Yes, I've 'abandoned' the thread in "Toubleshooting" in as much as I won't post into it again unless someone responds there. I decided that the thread better belongs in "Bug Reports" when I found out that earlier versions of uTorrent would download the same torrent without the errors being generated by uTorrent 3.3. As that is the case it just seems to me that 3.3 likely contains a bug in this respect. (In any case, if it is possible to delete the thread in Troubleshooting, please do - I looked for a way to do so myself but couldn't see one.)

Thanks for clarifying for me what you meant when saying that there may be a 'read only' problem in the issue that I have tried to describe. Okay, I'm no kind of an expert, but it sounds like a possibility.

However, I'd have to say that if that is the issue then it is uTorrent that is most likely generating it. I don't see how it can be anything that I'm doing as I haven't changed the way that I use 3.3 from earlier versions. And again, as the earlier versions will download identical torrents without these issues that to me does suggest that 3.3 is doing something untowards.

Again, I'd ask, has 3.3 in any way changed the way that it writes to disk? If it has then that would seem to be the most likely area to look to as being implicated in this issue.

Looking at the portion of log that I posted it looks to me like 3.3 is 'getting lost' in what location it is pointing to in a downloading file. But I really don't know, that's way beyond my level of expertise. I really don't know how to read that log with understanding, so I'm just making a wild guess that I wouldn't be surprised to find is incorrect anyway.

In any case, the problem was intermittent. By which I mean that it would be possible to download for sixty, ten, five, three, two minutes - then, bang, error. So 3.3 wasn't outright incapable of downloading at all, just intemittent errors that ended downloading until it was manually re-started (I always did a 'force recheck' before manually re-starting the torrent).

Thanks again for the response.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...