Page 1 of 2
Deluge keeps pause and resume by itself.
Posted: Sun Aug 05, 2007 7:49 pm
by mezz
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.
Code: Select all
no existing Deluge session
Starting new Deluge session...
deluge_core; using libtorrent 0.13.0.0. Compiled with NDEBUG.
Applying preferences
Pickling state...
Scanning plugin dir /usr/local/share/deluge/plugins
Initialising plugin TorrentCreator
Initialising plugin TorrentSearch
Initialising plugin BlocklistImport
Initialising plugin TorrentFiles
Initialising plugin TorrentPeers
Initialising plugin RSS
Initialising plugin TorrentNotification
Initialising plugin DesiredRatio
Initialising plugin NetworkHealth
Initialising plugin Locations
Initialising plugin SpeedLimiter
Initialising plugin NetworkGraph
Initialising plugin TorrentPieces
Initialising plugin EventLogging
Applying preferences
Starting DHT...
Showing window
Pickling state...
Pickling state...
Raising error: Handle not found.
Saving prefs...
Pickling state...
Stopping DHT...
Saving fastresume data...
Quitting the core...
core: removing torrents...
core: removing settings...
core: shutting down session...
core shut down.
FreeBSD 6.2-STABLE
boost-1.34.0
gtk-2.11.6
pygtk-2.10.6
python-2.5.1
I am running everything at bleed edge such as using GNOME 2.19.6, but stable version of FreeBSD.
Re: Deluge keeps pause and resume by itself.
Posted: Sun Aug 05, 2007 8:38 pm
by daddy
Yeah I get this periodically, too. On Gutsy/SVN and Feisty/0.5.3, both AMD64.
Re: Deluge keeps pause and resume by itself.
Posted: Sun Aug 05, 2007 8:40 pm
by markybob
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.
Code: Select all
no existing Deluge session
Starting new Deluge session...
deluge_core; using libtorrent 0.13.0.0. Compiled with NDEBUG.
Applying preferences
Pickling state...
Scanning plugin dir /usr/local/share/deluge/plugins
Initialising plugin TorrentCreator
Initialising plugin TorrentSearch
Initialising plugin BlocklistImport
Initialising plugin TorrentFiles
Initialising plugin TorrentPeers
Initialising plugin RSS
Initialising plugin TorrentNotification
Initialising plugin DesiredRatio
Initialising plugin NetworkHealth
Initialising plugin Locations
Initialising plugin SpeedLimiter
Initialising plugin NetworkGraph
Initialising plugin TorrentPieces
Initialising plugin EventLogging
Applying preferences
Starting DHT...
Showing window
Pickling state...
Pickling state...
Raising error: Handle not found.
Saving prefs...
Pickling state...
Stopping DHT...
Saving fastresume data...
Quitting the core...
core: removing torrents...
core: removing settings...
core: shutting down session...
core shut down.
FreeBSD 6.2-STABLE
boost-1.34.0
gtk-2.11.6
pygtk-2.10.6
python-2.5.1
I am running everything at bleed edge such as using GNOME 2.19.6, but stable version of FreeBSD.
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
Re: Deluge keeps pause and resume by itself.
Posted: Sun Aug 05, 2007 9:11 pm
by daddy
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.
Re: Deluge keeps pause and resume by itself.
Posted: Sun Aug 05, 2007 11:25 pm
by mezz
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?
Re: Deluge keeps pause and resume by itself.
Posted: Sun Aug 05, 2007 11:32 pm
by markybob
mezz wrote: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.
Re: Deluge keeps pause and resume by itself.
Posted: Mon Aug 06, 2007 12:46 am
by mezz
markybob wrote:mezz wrote: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.
dd if=/dev/zero of=sparse_file bs=1048576 count=1 seek=1048576
Re: Deluge keeps pause and resume by itself.
Posted: Mon Aug 06, 2007 12:52 am
by markybob
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.
dd if=/dev/zero of=sparse_file bs=1048576 count=1 seek=1048576
hrm, my bad. what's the magic number for ufs2 and ufs so i can fix it?
Re: Deluge keeps pause and resume by itself.
Posted: Mon Aug 06, 2007 3:11 am
by mezz
markybob wrote: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.
dd if=/dev/zero of=sparse_file bs=1048576 count=1 seek=1048576
hrm, my bad. what's the magic number for ufs2 and ufs so i can fix it?
I think the magic numbers are here: 0x011954 for UFS and 0x19540119 for UFS2
http://www.freebsd.org/cgi/cvsweb.cgi/s ... s/ffs/fs.h
Code: Select all
/*
* Filesystem identification
*/
#define FS_UFS1_MAGIC 0x011954 /* UFS1 fast filesystem magic number */
#define FS_UFS2_MAGIC 0x19540119 /* UFS2 fast filesystem magic number */
#define FS_BAD_MAGIC 0x19960408 /* UFS incomplete newfs magic number */
#define FS_OKAY 0x7c269d38 /* superblock checksum */
#define FS_42INODEFMT -1 /* 4.2BSD inode format */
#define FS_44INODEFMT 2 /* 4.4BSD inode format */
Code: Select all
# dumpfs ad4s1a | head -1
magic 19540119 (UFS2) time Sun Aug 5 20:06:43 2007
Re: Deluge keeps pause and resume by itself.
Posted: Mon Aug 06, 2007 3:19 am
by markybob
mezz wrote:markybob wrote: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.
dd if=/dev/zero of=sparse_file bs=1048576 count=1 seek=1048576
hrm, my bad. what's the magic number for ufs2 and ufs so i can fix it?
I think the magic numbers are here: 0x011954 for UFS and 0x19540119 for UFS2
http://www.freebsd.org/cgi/cvsweb.cgi/s ... s/ffs/fs.h
Code: Select all
/*
* Filesystem identification
*/
#define FS_UFS1_MAGIC 0x011954 /* UFS1 fast filesystem magic number */
#define FS_UFS2_MAGIC 0x19540119 /* UFS2 fast filesystem magic number */
#define FS_BAD_MAGIC 0x19960408 /* UFS incomplete newfs magic number */
#define FS_OKAY 0x7c269d38 /* superblock checksum */
#define FS_42INODEFMT -1 /* 4.2BSD inode format */
#define FS_44INODEFMT 2 /* 4.4BSD inode format */
Code: Select all
# dumpfs ad4s1a | head -1
magic 19540119 (UFS2) time Sun Aug 5 20:06:43 2007
ok, i've committed the change to svn trunk. give rev 1310 a shot and let me know how full allocation works or doesnt work
