I don't think that the checking feature is working properly. I had a nearly-completed torrent, but Deluge crashed. When I restarted it, the torrent was checked, and now told me that it was only 15% done. Can anyone suggest any possible explanations for this?
Pete
Checking is disappointing
-
- Member
- Posts: 10
- Joined: Sat Jan 10, 2009 10:22 pm
Re: Checking is disappointing
How big was the torrent?
On possible explanation could be that the data has not been written to the harddisk and was kept in RAM at the time of the crash.
On possible explanation could be that the data has not been written to the harddisk and was kept in RAM at the time of the crash.
Re: Checking is disappointing
I was downloading a single 175MB file from a very large torrent. The chunk size is 4MB.Chiphead2XS wrote:How big was the torrent?
On possible explanation could be that the data has not been written to the harddisk and was kept in RAM at the time of the crash.
If Deluge is behaving as you suggest, then I think that it's overvaluing performance at the expense of stability.
Pete
Re: Checking is disappointing
It will discard non-complete pieces and with a piece size of 4mb, you'd likely have a lot of those.
Re: Checking is disappointing
I had deluge 1.1.1 crash and I'm stuck with 198 torrents at "0.0%" checking.
Prior to that, I had to manually delete 25 torrents that were stuck in check (some would get to a percentage and stop).
Definitely a show stopper.
running 1.1.1 on gentoo.
gcc (Gentoo 4.3.2 p1.1) 4.3.2
(let me know if there is additional info I could provide that would be useful).
thanks,
andy
[edit] rebooted the machine (server, whatever) and restarted deluge and it seems to be checking pieces. I'll repost if it finishes or not. Brings up a question. In addition to the processes deluged starts owned by the assigned user, are there others that might be the problem?
thx,
andy
Prior to that, I had to manually delete 25 torrents that were stuck in check (some would get to a percentage and stop).
Definitely a show stopper.
running 1.1.1 on gentoo.
gcc (Gentoo 4.3.2 p1.1) 4.3.2
(let me know if there is additional info I could provide that would be useful).
thanks,
andy
[edit] rebooted the machine (server, whatever) and restarted deluge and it seems to be checking pieces. I'll repost if it finishes or not. Brings up a question. In addition to the processes deluged starts owned by the assigned user, are there others that might be the problem?
thx,
andy
Re: Checking is disappointing
hi guys,
are there some ppl still having problems with very huge torrents?
i very often got some stuck torrents when it gets to checking files after i restart the deluged.
recently a 21GB torrent stucks when started.
i mean, man this is really huge, but that shouldn't be a problem.
i've got some time to wait to get checking and downloading finished
specs:
ubuntu 8.10
deluge 1.1.3
startup script
startup script:
anybody any ideas?
bye, darude
are there some ppl still having problems with very huge torrents?
i very often got some stuck torrents when it gets to checking files after i restart the deluged.
recently a 21GB torrent stucks when started.
i mean, man this is really huge, but that shouldn't be a problem.
i've got some time to wait to get checking and downloading finished
specs:
ubuntu 8.10
deluge 1.1.3
startup script
startup script:
Code: Select all
#!/bin/sh
# created by mambang
# Headless deluge startup script
#
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
USER="deluge"
DELUGEDAEMON="/usr/bin/deluged"
DELUGEDAEMON_OPTIONS="-d"
#DELUGEDAEMON_OPTIONS="-d -L debug --logfile=/var/log/deluge/deluged.log"
#DELUGEDAEMON_OPTIONS="-d -l /var/log/deluge/deluged.log"
WEBDAEMON="/usr/bin/deluge"
WEBDAEMON_OPTIONS="-u web"
DESC1="Deluge Daemon"
DESC2="Deluge WebUI"
NAME1="deluge daemon"
NAME2="deluge webui"
set -e
case "$1" in
start)
echo -n "Starting $DESC1 : "
start-stop-daemon -c $USER --start --background --quiet --exec $DELUGEDAEMON -- ${DELUGEDAEMON_OPTIONS}
echo "$NAME1"
sleep 2
echo -n "Starting $DESC2 : "
start-stop-daemon -c $USER --start --background --quiet --exec $WEBDAEMON -- ${WEBDAEMON_OPTIONS}
echo "$NAME2"
;;
stop)
echo -n "Stopping $DESC1 : "
PIDDELUGE=`ps ax |grep deluged |sed -n 1p |awk '{print $1}'`
kill $PIDDELUGE
echo "$NAME1."
echo -n "Stopping $DESC2 : "
PIDWEB=`ps ax |grep 'deluge -u web' |sed -n 1p |awk '{print $1}'`
kill $PIDWEB
echo "$NAME2."
;;
*)
N=deluge-daemon
echo "Usage: $N {start|stop}" >&
exit 1
;;
esac
bye, darude