qweqwe Posted March 9, 2009 Report Share Posted March 9, 2009 i have been monitoring this for a while and i believe it to be a utorrent bugthis has occured on both xp32 and vista64 networksutorrent 1.6 to present betasystem is 1 fileserver and 1 user pcrunning utorrent on the user pc and storing data on fileserverit will run perfectly fine if the torrent files are small-ish e.g max 30gbhowever if i run, as i am now 3 torrent files, 1x130gb,1x60gb and 1x40gb (this is tosec stuff btw)it will eventually bomb out taking the network drives out of action for the user pcgiving The network path was not found error on all torrentsthe network drives are still accessable from laptop or other pc's if put on the network after, just not from the user pcif i store the torrents on the local user pc drive, all is finebittornado does not give this error, ever, running exact same 3 torrents, so this points to a utorrent bugany ideas on this problemany questions, please askThanks Link to comment Share on other sites More sharing options...
Firon Posted March 9, 2009 Report Share Posted March 9, 2009 You're probably hitting an open file-handle limit for network paths with such a huge torrent, since TOSEC torrents have tons and tons of files... Link to comment Share on other sites More sharing options...
qweqwe Posted March 10, 2009 Author Report Share Posted March 10, 2009 Is there any chance of this being 'fixed' in utorrent as i much prefer it to using bittornado Link to comment Share on other sites More sharing options...
Firon Posted March 13, 2009 Report Share Posted March 13, 2009 Are you doing a force re-check when this happens, or just torrenting normally? Link to comment Share on other sites More sharing options...
qweqwe Posted March 14, 2009 Author Report Share Posted March 14, 2009 just normally. i believe if the torrent is over 50ish gb this happens. even more so if a few (3 or more) torrents are running together (leeching and seeding). i dont believe it has anything to do with the filecounts as these are iso tosec sets.the disk based tosec sets have many thousands more files but have no trouble (approx 10gb sized).updatethe bug also happens hereif i am downloading a torrent (18gb) to the fileserver no problems on its ownif i then attempt to download the 60gb torrent to the local drive, it eventually kills the 18gb torrent with the same error: The specified network name is no longer available. Link to comment Share on other sites More sharing options...
arvid Posted March 16, 2009 Report Share Posted March 16, 2009 If it's not related to the number of files, maybe it's related to the size of the largest file?Is that a single 130 GB iso or is it split up into smaller DVDs like 4 GB or 8 GB images?Also, you have this problem by seeding these large torrents alone, right? Or does it only happen when you download? Link to comment Share on other sites More sharing options...
qweqwe Posted March 16, 2009 Author Report Share Posted March 16, 2009 to be honest i dont think it isthe largest file is probably 600mb in the torrents. these are tosec iso torrents.to be honest i cant get to the seeding stage to test it natrually. if i download the 130gb torrent to local drive and then move it to the server it still does the error when part way through checking the torrent. so in answer the bug can happen at any time or state.i personally believe it is something to do with the total size of the torrent but i can't say why as it only seems to happen on 40gb+ torrents. Link to comment Share on other sites More sharing options...
arvid Posted March 16, 2009 Report Share Posted March 16, 2009 From looking at the BitTornado source, the only significant difference I can see is that you optionally can lock files while they are open. Do you know if you use this option?The other thing I can see is that it calls fsync() before reading files.Btw. In uTorrent, did you try play around with the disk IO options? It might help to uncheck the "Disable Windows caching of disk writes". This wouldn't explain why it didn't work in versions all the way back to 1.6 though. Link to comment Share on other sites More sharing options...
qweqwe Posted March 17, 2009 Author Report Share Posted March 17, 2009 i use bittornado with default optionsi have unchecked "Disable Windows caching of disk writes" and am testing now but so far so goodi'll give an update after i have torture tested itthanks for relpys do far by the wayall good so far, no errors occuredwill keep on testing and keep you all updated****UPDATE*****no its still doing it[2009-03-23 07:07:08] IO Error:64 line:400 align:1 pos:1584485580 count:16384 actual:-99[2009-03-23 07:07:08] IO Error:64 line:650 align:512 pos:1584485580 count:16384 actual:0it seems once it has done it once, then the error occurs easier Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.