albrnick Posted January 5, 2006 Report Share Posted January 5, 2006 Hello! I've got a torrent with several hundred files. After my computer crashed, when I try to continue DLing that torrent, it errors out around 60% of the way through "checking" the torrent initially with the message: "Error: The system cannot open the file". I'm assuming something got corrupt when the computer crashed. I'd love to delete the file, but I've no idea which one failed. Is there anyway to figure out which file could not be opened in the torrent? Thanks for your time, -Nick Link to comment Share on other sites More sharing options...
Animorc Posted January 5, 2006 Report Share Posted January 5, 2006 Rightclick the torrent and select Force Re-check. That way, the corrupt pieces should be deleted. Link to comment Share on other sites More sharing options...
splintax Posted January 5, 2006 Report Share Posted January 5, 2006 I'd imagine the Log tab would be able to yield some useful info. edit: Sorry, the Logger tab. Oh, and Animorc, to me it looks like µT is already trying to re-check the file, and failing 60% through, like there is a problem with the .torrent or something? :| Link to comment Share on other sites More sharing options...
albrnick Posted January 5, 2006 Author Report Share Posted January 5, 2006 Thanks for the responses! Animorc: Re: Force Re-check. Same error as before. 60% throughSplintax: Re: Logger tab. Yeah, I had hopes something would show up there, but just seems to be peer to peer type traffic, not file system stuff. Good idea on the torrent, I'll re download that and see what happens. = ) Thanks! -Nick Link to comment Share on other sites More sharing options...
albrnick Posted January 5, 2006 Author Report Share Posted January 5, 2006 Well, redownloaded the torrent, and still the same issue. Any ideas on how I can figure out what file it can't open? Thanks for your time, -Nick Link to comment Share on other sites More sharing options...
splintax Posted January 6, 2006 Report Share Posted January 6, 2006 Hmm. I hate to suggest it, but maybe in the meantime (until someone with an idea comes along), you could try another torrent client and see if that works? Link to comment Share on other sites More sharing options...
Switeck Posted January 6, 2006 Report Share Posted January 6, 2006 You may want to run a manually started SCANDISK on that hard drive.Sounds like there's more damage than just to torrent files... Link to comment Share on other sites More sharing options...
chaosblade Posted January 6, 2006 Report Share Posted January 6, 2006 you can use process explorer from sysinternals (google it) to see what other program is using that file handle, try freeing it and so on. Link to comment Share on other sites More sharing options...
albrnick Posted January 6, 2006 Author Report Share Posted January 6, 2006 So here is what all else I tried, and what worked. After not being able to find the file, I wrote a program that went and opened every file, and read all the data in it, hoping I could figure out what file was causing probs. Unfortunately, it successfully read all the files just fine. So then I realized that I was using a mapped network drive. Which worked just fine when the torrent was new, but perhaps with all the data to go through (Several gigs), is having issues? (At the same spot?!?) So I copied the torrent to a local drive, and it has worked just fine. So I suspect it had to do with it being a network drive? Thanks everyone for their help! I hope this thread helps someone in the future. -Nick Link to comment Share on other sites More sharing options...
Redleer Posted January 6, 2006 Report Share Posted January 6, 2006 this mayby helps if someone with same problem knows how to use search on forums Link to comment Share on other sites More sharing options...
splintax Posted January 7, 2006 Report Share Posted January 7, 2006 yeah. Interesting. If we can get people confirming this issue (large amounts/total file sizes) over the network, then it should go in the FAQ.albrnick: Can you tell us how many files were in the folder, and the total size of the folder? Link to comment Share on other sites More sharing options...
Firon Posted January 7, 2006 Report Share Posted January 7, 2006 1.3 stable doesn't work well when writing across the network, but the betas do.I used a 31GB torrent across the network, so I know it works. Link to comment Share on other sites More sharing options...
Perseid Posted September 17, 2006 Report Share Posted September 17, 2006 I realize this is a very old post but it came up in a google search. Anyway, I can confirm this bug and that it still exists in 1.6. A large torrent of many small files would say "File could not be opened" about 40% of the way through a recheck when running over a network drive. Moving it to a local drive made it work just fine.And I don't know if this is a clue as to how to fix it, but I also had another large torrent running over the same network drive and the instant the force recheck on the non-working torrent failed the working torrent stopped as well.Finally, uTorrent is not the only program that had these problems. BitComet and BitTornado all did similar things. Maybe it's Windows. Link to comment Share on other sites More sharing options...
boxster Posted November 4, 2007 Report Share Posted November 4, 2007 Yes, I am aware this is an antique thread, however I am having the same problem with uTorrent 1.7.5I have a torrent with ~17000 files which is stored on a samba share under Linux. During the check phase, uTorrent the torrent is stopped with an error: "Error: The system cannot open the file." The log contains errors of the form: [22:22:22] Error opening "\\machine\directory\file":After digging into the problem, I realized uTorrent is reaching the 10000 open file limit of Samba. If I delete roughly 7000 files, the torrent proceeds to the download state. The shortened output from smbstatus:8703 500 DENY_NONE 0x20089 RDONLY EXCLUSIVE+BATCH /directory Share/Path/File1 Sat Nov 3 22:26:37 20078703 500 DENY_NONE 0x20089 RDONLY EXCLUSIVE+BATCH /directory Share/Path/File2 Sat Nov 3 22:28:20 20078703 500 DENY_NONE 0x20089 RDONLY EXCLUSIVE+BATCH /directory Share/Path/File3 Sat Nov 3 22:28:15 2007And finally, the output of 'smbstatus | wc' as the failure approched:[root@machine etc]# smbstatus -L | wc 9304 120912 1582297[root@machine etc]# smbstatus -L | wc 9805 127425 1666086[root@machine etc]# smbstatus -L | wc 9882 128426 1678917[root@machine etc]# smbstatus -L | wc 9921 128933 1685420[root@machine etc]# smbstatus -L | wc 9951 129323 1690426[root@machine etc]# smbstatus -L | wc 9977 129661 1694779[root@machine etc]# smbstatus -L | wc 9999 129947 1698446< At this point the torrent stopped>[root@machine etc]# smbstatus -L | wc 6209 80677 1055235[root@machine etc]# smbstatus -L | wc 1328 17224 224343[root@machine etc]# smbstatus -L | wc 95 1195 15537[root@machine etc]# smbstatus -L | wc 95 1195 15537So, can a developer reproduce this failure?Box Link to comment Share on other sites More sharing options...
Firon Posted November 4, 2007 Report Share Posted November 4, 2007 1.8 was already fixed to close open files when it's done checking them. I don't know of any workaround, apart from increasing the open file limit. Link to comment Share on other sites More sharing options...
blarrrg Posted August 3, 2008 Report Share Posted August 3, 2008 So there's no way to fix this in 1.7.7? I moved some large torrents across to a network drive to seed and I get this no matter what I do. They're all 20+ GB with at least 2000 files in them, no more than 3000 files. It'd really be nice to be able to seed them from the network drive, and all betas/RCs are banned from the tracker I'm seeding them at so upgrading to RC6 isn't really an option. I got one torrent with ~1500 files in it to work, but any that have more than that aren't. Link to comment Share on other sites More sharing options...
DreadWingKnight Posted August 3, 2008 Report Share Posted August 3, 2008 We aren't backporting any fixes like this to 1.7.x, so you either convince your tracker admin to unban 1.8 or you wait. Link to comment Share on other sites More sharing options...
Firon Posted August 5, 2008 Report Share Posted August 5, 2008 1.7.7's development is done and dead, so you'll have to wait for 1.8. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.