I am maintainer for deluge on FreeBSD ports tree. I have not update to 0.5.3 and 0.5.4, because I couldn't figure how to debug it. For some reason, at 0.5.3, deluge would start to behave weird. When I add a new torrent and it would download fine for a few seconds, then all suddent it will pause and resume in loop at the every a few seconds. It reset the download everytime too, include the status. The output doesn't show anything and I also have tried to remove ~/.config/deluge with no different result.
mezz wrote:I am maintainer for deluge on FreeBSD ports tree. I have not update to 0.5.3 and 0.5.4, because I couldn't figure how to debug it. For some reason, at 0.5.3, deluge would start to behave weird. When I add a new torrent and it would download fine for a few seconds, then all suddent it will pause and resume in loop at the every a few seconds. It reset the download everytime too, include the status. The output doesn't show anything and I also have tried to remove ~/.config/deluge with no different result.
I download all my torrents to an NFS mount, so that could be the issue--I don't usually use compact allocation, but next time this happens I'll double check it.
markybob wrote:freebsd...so ufs2? for that you need to use compact allocation for deluge to work properly. just activate it in preference and you should be fine
Yep, it's UFS2. I have enabled compact allocation and it solves my problem. Thanks! Why it doesn't happen in 0.5.2 and older versions?
markybob wrote:freebsd...so ufs2? for that you need to use compact allocation for deluge to work properly. just activate it in preference and you should be fine
Yep, it's UFS2. I have enabled compact allocation and it solves my problem. Thanks! Why it doesn't happen in 0.5.2 and older versions?
because we werent using sparse files back then. ufs2, unfortunately, doesnt have sparse file support.
markybob wrote:freebsd...so ufs2? for that you need to use compact allocation for deluge to work properly. just activate it in preference and you should be fine
Yep, it's UFS2. I have enabled compact allocation and it solves my problem. Thanks! Why it doesn't happen in 0.5.2 and older versions?
because we werent using sparse files back then. ufs2, unfortunately, doesnt have sparse file support.
Not true, UFS and UFS2 do have sparse file support. I can do like this below on both UFS and UFS2. Can you point me to which source file? Thanks.
mezz wrote:
Not true, UFS and UFS2 do have sparse file support. I can do like this below on both UFS and UFS2. Can you point me to which source file? Thanks.
mezz wrote:
Not true, UFS and UFS2 do have sparse file support. I can do like this below on both UFS and UFS2. Can you point me to which source file? Thanks.
mezz wrote:
Not true, UFS and UFS2 do have sparse file support. I can do like this below on both UFS and UFS2. Can you point me to which source file? Thanks.
Deluge
