Hi Eugene,

just thought i throw in my experience also.

I once had similar issues. Hash errors solved by multiple tries.
Safe_sync was helping a little but the error still remained.
In my case one of the two RAM sticks was faulty (memtest was spilling
red all over the place LOL).
Began after around 6-8 months after purchase and i needed 3-4 months
until i finally found the cause.


Eugene Zaretskiy schrieb:
> On Tue, Nov 24, 2009 at 5:40 AM, Jari Sundell
> <[email protected]> wrote:
>   
>> On Tue, Nov 24, 2009 at 2:11 PM, Eugene Zaretskiy <[email protected]> 
>> wrote:
>>     
>>> So now I know:
>>>
>>> 1) It's not the filesystem, as both ext3 and ext4 are having this issue.
>>> 2) It's not the hardware
>>> 3) It's not the raid configuration
>>>       
>> Experience has shown that these problems invariably gets fixed when
>> the user downgrades/upgrades/changes the system in some way, leading
>> to the conclusion that the problem lies somewhere between the mmap
>> system calls and hardware.
>>
>> You're not going to convince me otherwise unless you have a trace of
>> all the mmap/munmap/msync calls and can show that rtorrent calls them
>> in the wrong order or drops some. There is a reason why rtorrent has
>> been used to detect and debug so many mmap, FS and other bugs.
>>     
>
> I'm sure you're right. In fact, I likely didn't do enough testing of
> the issue before posting here but I thought I'd seek the advice of
> those on the list as to what I should do next -- I apologize in
> advance if this is mis-use of the list. In any case, I'm going to try
> a. phantom's advice next, this is exactly the sort of help I was
> seeking, thanks.
>
>   
>>> I'm sorry, but it really looks like an rtorrent issue to me. If those
>>> here disagree, I would kindly request their advice on what next steps
>>> I can take? I am fully prepared to "play around" with my
>>> configuration, I can format my drives to any filesystem you please, or
>>> modify my configuration in any way that would help those here diagnose
>>> the problem if they wish.
>>>
>>> I appreciate anyone's input on this situation... been reformatting
>>> drives and moving data around for days now and really don't know what
>>> to do next.
>>>       
>> Try reverting the system to the last known good state, e.g. before a
>> kernel update or what ever you did before things started not working.
>>     
>
> Unfortunately, the last known good state is Windows, without rtorrent.
> I last used rtorrent on an entirely different machine with a different
> version of rtorrent, the kernel, etc, a long time ago. Unfortunately,
> Windows is no longer acceptable from a licensing perspective and in
> any case I prefer rtorrent to utorrent anyway (unless you start
> bundling the Ask.com search bar for lynx or something?)
>
>   
>> Jari
>>
>>     
>
>
>
>   

_______________________________________________
Libtorrent-devel mailing list
[email protected]
http://rakshasa.no/mailman/listinfo/libtorrent-devel

Reply via email to