On Nov 2, 2007, at 7:46 PM, Anders Andersson wrote:
Even better, since most platforms already have solutions for handling
this problem, just leave it up to the user/os. We have user/group
quotas (hard/soft), we have drive partitioning,
First of all, how many users actually set up quotas?
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. In the
past, this lead to many, many problems with data corruption and
rtorrent unknowingly sending bad data. So, setting up a quota does
not in fact fix this problem either. It just moves the point of where
the disk (for the user) is full to a point where the disk itself is
not full, just the user's quota.
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.
and we have the "leave
1% of the drive for root only" protection for ext2.
You're not running rtorrent as root, are you?! Otherwise, how does
that help?
--
Josef Drexler
[EMAIL PROTECTED]
_______________________________________________
Libtorrent-devel mailing list
[email protected]
http://rakshasa.no/mailman/listinfo/libtorrent-devel
