[workarounds] DISK OVERLOAD and stuck torrents

[NetworkPro]

Hello,

since a lot of versions (more than a year already), when downloading huge torrents

the utorrent process fails miserably and has to be restarted - sometimes with disk overloaded sometimes it crashes before I can see the overload message

this happens under Win7x64, Win8x64 on Asmedia SATA and Intel SATA as well. (latest drivers) but I think the thing that causes the crash is either .torrent files or some packets that come in or combination of these

At the moment I blame the utorrent developers for failing to produce a working software. Because such bugs are not seen on the other torrent clients.

If you want "a quality bug report" - invest in QA department.

[DreadWingKnight]

Considering the quality of your bug report.

I'd say it's not actually uTorrent's fault.

[NetworkPro]

And you will be the one to judge because you are?

Best I can do is to replicate the problem in a virtual instance of Windows with some free space to download the huge torrents in question.

Someone from BitTorrent, Inc may email me with the access details and I will do my best to get them speedy results.

Then they can poke at the VM and uTorrent config I used all they want.

I think the issue comes from combination of .torrent file + the software, that's the justification for this.

[rafi]

Only under VM?

[NetworkPro]

Ah yes , I will replicate if the guys provide native hardware based environment as well. I am not limited by a VM.

[rafi]

What size of torrent/space? With 3.3.x?

[NetworkPro]

Latest version. (3.3.1.30059)

I've seen problems with 3GBs + but the last one that wasted me time was around 30gig. Had to wait for "recheck" :mad: (good that you have mad smiley icon)

50+ Gbytes of free space can suffice.

[rafi]

I didn't even know there was such build... http://user.utorrent.com/downloads/win Maybe use the official build...

Crashing with 3G files? I have done plenty w/o any issue... Must be something at your end.

Try run-as-admin + my settings + pref->adv->diskio.sparse_files -true

[NetworkPro]

Build came through Check for Update

Good suggestion but I prefer to not run as admin. As I remember I tried that and it was still happening.

Connection speeds around here are more than 5mbps up and more than 50 down, often reaching 100/100.

So can you guys help for the suggested test?

[rafi]

Not before you've done that:

Try run-as-admin + my settings + pref->adv->diskio.sparse_files -true

Preferably with one of the downloadable builds...

And you better disable/uninstall any AV you have installed there...

Oh, and if you post this build somewhere, I can try and test with it too ...

[NetworkPro]

OK ok you dont have to be an nasty about it ?

A while ago we came to the conclusion that sparse files would not be useful. They only increase disk fragmentation.

[rafi]

I said my-settings (below, tuned to your bandwidth/paths) +sparse

And volunteering to test your build is not too nasty...

[NetworkPro]

utorrent3.3.1.30059.rar http://www.sendspace.com/file/o198nx

The settings that I end up using are cranked up for speed

settings_dat.rar http://www.sendspace.com/file/zgdti8

With many builds during the past year, I have tested with unchanged default settings as well, and the problems persisted so I kept using the speed settings.

Thank you.

[rafi]

Still no issues... Your dat file seems to be deleted... used mine.

http://torrentz.eu/search?f=CentOS-6.4-x86_64-bin-DVD1to2

[NetworkPro]

Sparse files does the trick it seems.

But what about the unwanted fragmentation?

[rafi]

What do you mean ? + using my settings? Per-allocate enabled as well? SSD/Sata drive?

[NetworkPro]

Pre-allocate is enabled.

I checked your settings.dat with the bencode editor and I chose one by one what fits the situation that I have and ended up having a third completely different settings.dat even more cranked up.

One of the drives that test lately on is SATA SAMSUNG HD154UI Revision 1AG01118

[rafi]

Pre-allocate is enabled.

Which, btw, is very weird, because per the help file this should neutralize the sparse option ...

But, bugs have no logic...

Can you post/share your settings file?

[NetworkPro]

The more and the bigger torrents I was trying to download - the more frequent the bugs encountered.

- new torroents stuck at allocating as if the storage subsystem of uttorent is stuck

- when bug is noticed, exit utorrent was not enough, had to kill process

- sometimes seeding went down with time - on utorrent restart - seeding resumed

- sometimes utorrent was stuck at Disk Overloaded 100% until the proecss was killed and relaunched

I have just replaced the uttorent.exe with the latest 3.3.2 RC. which so far seems better.

The settings.dat do not seem to make much difference. Other people need me to seed, so most of the related numbers/limits I crank for that.

Some trackers don't yet allow 3.3.2.0 so now I have to use Transmission as well for some stuff.

[rafi]

I have just replaced the uttorent.exe with the latest 3.3.2 RC. which so far seems better.

With sparse still enabled?

[NetworkPro]

pre-allocate=yes

sparse=false

to avoid fragmentation :|

[rafi]

pre-allocate=yes

sparse=false

to avoid fragmentation :|

Sparse files does the trick it seems.

But what about the unwanted fragmentation?

And what about your "does the trick" recommendation ? ... FYI, nothing was changed in 3.3.2 in that regard...

[NetworkPro]

Apparently something was changed But now a bunch of torrents are not truly seeded because the trackers refuse the new version so the amount of things that the utorrent client needs to keep track of is less.

[ciaobaby]

because the trackers refuse the new version so the amount of things that the utorrent client needs to keep track of is less.

Not true, trackers timing out and the like means that the client is wasting clock cycles trying to communicate with them.

[NetworkPro]

your post is not true