On 11/2/07, Josef Drexler <[EMAIL PROTECTED]> wrote: > Secondly, the problem is that when the disk is full, rtorrent thinks > the data was written correctly, but space isn't actually allocated > until the filesystem attempts to sync the buffer. This is because > rtorrent is using mmapped files and writing to sparse files non- > sequentially. Thus, when the disk full condition is detected, it is > already far too late and data corruption has already occurred. Exactly. I lost my MC configuration because of disk full. That was nasty. :-) And sometimes rtorrent run over (actually below) 500MB limit. Now I understand why. :-)
> Hence, removing this from the default configuration would a very bad > move. If you personally are confident that you are capable of > preventing such problems on your system, including an understanding > of how they occur when using mmapped writes to sparse files, then you > may of course disable this feature. Instructions have been provided > already. I have no problem with automatic stop that is great feature indeed but I would like to stop only "active" torrent and keep seed only torrent running. And OS doesn't know anything about my torrents just rtorrent. bye, a _______________________________________________ Libtorrent-devel mailing list [email protected] http://rakshasa.no/mailman/listinfo/libtorrent-devel
