Arch Linux

agkbill

Member

Registered: 2011-06-13

Posts: 85

[SOLVED] rtorrent. Caught Bus error dumping stack.

Hi,

I am experience problems with rtorrent, it have been running very nice for some weeks. But not any more.

I get:

christer ~ $ rtorrent
Caught Bus error, dumping stack:
Stack dump not enabled.
A bus error probably means you ran out of diskspace.
Aborted
christer ~ $

When I check diskspace it looks like that is not the issue here.

christer ~ $ df
Filesystem      Size  Used Avail Use% Mounted on
udev             10M     0   10M   0% /dev
run              10M  168K  9.9M   2% /run
/dev/sda3        12G  4.2G  6.9G  38% /
shm             120M     0  120M   0% /dev/shm
/dev/sdb1        76G   32G   41G  44% /media/torr
christer ~ $

Folders belongin to rtorrent are located on a external USB disk /dev/sdb

-Downloads
-torrents
-session

I mount the USB disk at /media/torr.

Disks look like.

christer ~ $ sudo fdisk -ls
Password: 

Disk /dev/sda: 40.0 GB, 40007761920 bytes
255 heads, 63 sectors/track, 4864 cylinders, total 78140160 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00077627

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1            2048    52537343    26267648   83  Linux
/dev/sda2        77160195    78140159      489982+  83  Linux
/dev/sda3   *    52537344    77160194    12311425+  83  Linux

Partition table entries are not in disk order

Disk /dev/sdb: 82.0 GB, 81963515904 bytes
255 heads, 63 sectors/track, 9964 cylinders, total 160084992 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00096092

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1            2048   160083967    80040960   83  Linux
christer ~ $ 

Any ideas what it could be or how to pinpoint what the problem is?

Thank you!

All the best.
/Christer

Last edited by agkbill (2011-07-10 09:41:27)

Inxsible

Forum Fellow

From: Chicago

Registered: 2008-06-09

Posts: 9,183

Re: [SOLVED] rtorrent. Caught Bus error dumping stack.

Can we see your rtorrent.rc ?

---

Forum Rules

There's no such thing as a stupid question, but there sure are a lot of inquisitive idiots !

agkbill

Member

Registered: 2011-06-13

Posts: 85

Re: [SOLVED] rtorrent. Caught Bus error dumping stack.

My rtorrent.rc file.

# This is an example resource file for rTorrent. Copy to
# ~/.rtorrent.rc and enable/modify the options as needed. Remember to
# uncomment the options you wish to enable.

# Maximum and minimum number of peers to connect to per torrent.
min_peers = 80
max_peers = 200

# Same as above but for seeding completed torrents (-1 = same as downloading)
min_peers_seed = 10
max_peers_seed = 2000

# Maximum number of simultanious uploads per torrent.
max_uploads = 100

# Global upload and download rate in KiB. "0" for unlimited.
download_rate = 0
upload_rate = 0

# Default directory to save the downloaded torrents.
directory = /media/torr/Downloads

# Default session directory. Make sure you don't run multiple instance
# of rtorrent using the same session directory. Perhaps using a
# relative path?
session = /media/torr/session

# Watch a directory for new torrents, and stop those that have been
# deleted.
schedule = watch_directory,5,5,load_start=/media/torr/torrents/*.torrent
#schedule = untied_directory,5,5,stop_untied=

# Close torrents when diskspace is low.
#schedule = low_diskspace,5,60,close_low_diskspace=100M

# Stop torrents when reaching upload ratio in percent,
# when also reaching total upload in bytes, or when
# reaching final upload ratio in percent.

# Enable the default ratio group
ratio.enable=

# Changes the limits
ratio.min.set=100
ratio.max.set=600
ratio.upload.set=9000000M
# Changing the command triggered when the ration is reached
system.method.set = group.seeding.ratio.command, d.close=, d.erase=

# The ip address reported to the tracker.
#ip = 127.0.0.1
#ip = rakshasa.no

# The ip address the listening socket and outgoing connections is
# bound to.
#bind = 127.0.0.1
#bind = rakshasa.no

# Port range to use for listening.
#port_range = 6890-6999

# Start opening ports at a random position within the port range.
#port_random = no

# Check hash for finished torrents. Might be usefull until the bug is
# fixed that causes lack of diskspace not to be properly reported.

# Stop torrents when reaching upload ratio in percent,
# when also reaching total upload in bytes, or when
# reaching final upload ratio in percent.

# Enable the default ratio group
ratio.enable=

# Changes the limits
ratio.min.set=100
ratio.max.set=600
ratio.upload.set=9000000M
# Changing the command triggered when the ration is reached
system.method.set = group.seeding.ratio.command, d.close=, d.erase=

# The ip address reported to the tracker.
#ip = 127.0.0.1
#ip = rakshasa.no

# The ip address the listening socket and outgoing connections is
# bound to.
#bind = 127.0.0.1
#bind = rakshasa.no

# Port range to use for listening.
#port_range = 6890-6999

# Start opening ports at a random position within the port range.
#port_random = no

# Check hash for finished torrents. Might be usefull until the bug is
# fixed that causes lack of diskspace not to be properly reported.
#check_hash = no

# Set whetever the client should try to connect to UDP trackers.
#use_udp_trackers = yes

agkbill

Member

Registered: 2011-06-13

Posts: 85

Re: [SOLVED] rtorrent. Caught Bus error dumping stack.

I did a check of the file system and it does not look to good.

Is this something that is possible to correct or is it simply the end of my hard drives life?

 [root@arch ~]# fsck.reiserfs /dev/sdb
reiserfsck 3.6.21 (2009 www.namesys.com)

*************************************************************
** If you are using the latest reiserfsprogs and  it fails **
** please  email bug reports to reiserfs-list@namesys.com, **
** providing  as  much  information  as  possible --  your **
** hardware,  kernel,  patches,  settings,  all reiserfsck **
** messages  (including version),  the reiserfsck logfile, **
** check  the  syslog file  for  any  related information. **
** If you would like advice on using this program, support **
** is available  for $25 at  www.namesys.com/support.html. **
*************************************************************

Will read-only check consistency of the filesystem on /dev/sdb
Will put log info to 'stdout'

Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes

reiserfs_open: the reiserfs superblock cannot be found on /dev/sdb.
Failed to open the filesystem.

If the partition table has not been changed, and the partition is
valid  and  it really  contains  a reiserfs  partition,  then the
superblock  is corrupted and you need to run this utility with
--rebuild-sb.

[root@arch ~]# fsck.reiserfs --rebuild-sb /dev/sdb
reiserfsck 3.6.21 (2009 www.namesys.com)

*************************************************************
** If you are using the latest reiserfsprogs and  it fails **
** please  email bug reports to reiserfs-list@namesys.com, **
** providing  as  much  information  as  possible --  your **
** hardware,  kernel,  patches,  settings,  all reiserfsck **
** messages  (including version),  the reiserfsck logfile, **
** check  the  syslog file  for  any  related information. **
** If you would like advice on using this program, support **
** is available  for $25 at  www.namesys.com/support.html. **
*************************************************************

Will check superblock and rebuild it if needed
Will put log info to 'stdout'

Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes

reiserfs_open: the reiserfs superblock cannot be found on /dev/sdb.

what the version of ReiserFS do you use[1-4]
    (1)   3.6.x
    (2) >=3.5.9 (introduced in the middle of 1999) (if you use linux 2.2, choose this one)
    (3) < 3.5.9 converted to new format (don't choose if unsure)
    (4) < 3.5.9 (this is very old format, don't choose if unsure)
    (X)   exit
1

Enter block size [4096]: 
4096

No journal device was specified. (If journal is not available, re-run with --no-journal-available option specified).
Is journal default? (y/n)[y]: 

Did you use resizer(y/n)[n]: 
rebuild-sb: no uuid found, a new uuid was generated (cba745da-5338-462b-9c72-0e00d06b27ea)

rebuild-sb: You either have a corrupted journal or have just changed
the start of the partition with some partition table editor. If you are
sure that the start of the partition is ok, rebuild the journal header.
Do you want to rebuild the journal header? (y/n)[n]: y
Reiserfs super block in block 16 on 0x810 of format 3.6 with standard journal
Count of blocks on the device: 20010624
Number of bitmaps: 611
Blocksize: 4096
Free blocks (count of blocks - used [journal, bitmaps, data, reserved] blocks): 0
Root block: 0
Filesystem is NOT clean
Tree height: 0
Hash function used to sort names: not set
Objectid map size 0, max 972
Journal parameters:
    Device [0x0]
    Magic [0x0]
    Size 8193 blocks (including 1 for journal header) (first block 18)
    Max transaction length 1024 blocks
    Max batch size 900 blocks
    Max commit age 30
Blocks reserved by journal: 0
Fs state field: 0x1:
     some corruptions exist.
sb_version: 2
inode generation number: 0
UUID: cba745da-5338-462b-9c72-0e00d06b27ea
LABEL: 
Set flags in SB:
Mount count: 1
Maximum mount count: 30
Last fsck run: Fri Jul  8 17:47:27 2011
Check interval in days: 180
Is this ok ? (y/n)[n]: y
The fs may still be unconsistent. Run reiserfsck --check.

[root@arch ~]# fsck.reiserfs /dev/sdb
reiserfsck 3.6.21 (2009 www.namesys.com)

*************************************************************
** If you are using the latest reiserfsprogs and  it fails **
** please  email bug reports to reiserfs-list@namesys.com, **
** providing  as  much  information  as  possible --  your **
** hardware,  kernel,  patches,  settings,  all reiserfsck **
** messages  (including version),  the reiserfsck logfile, **
** check  the  syslog file  for  any  related information. **
** If you would like advice on using this program, support **
** is available  for $25 at  www.namesys.com/support.html. **
*************************************************************

Will read-only check consistency of the filesystem on /dev/sdb
Will put log info to 'stdout'

Do you want to run this program?[N/Yes] (note need to type Yes if you do):yes
[root@arch ~]# fsck.reiserfs /dev/sdb
reiserfsck 3.6.21 (2009 www.namesys.com)

*************************************************************
** If you are using the latest reiserfsprogs and  it fails **
** please  email bug reports to reiserfs-list@namesys.com, **
** providing  as  much  information  as  possible --  your **
** hardware,  kernel,  patches,  settings,  all reiserfsck **
** messages  (including version),  the reiserfsck logfile, **
** check  the  syslog file  for  any  related information. **
** If you would like advice on using this program, support **
** is available  for $25 at  www.namesys.com/support.html. **
*************************************************************

Will read-only check consistency of the filesystem on /dev/sdb
Will put log info to 'stdout'

Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes
###########
reiserfsck --check started at Fri Jul  8 17:48:45 2011
###########
Replaying journal: Done.
Reiserfs journal '/dev/sdb' in blocks [18..8211]: 0 transactions replayed
Zero bit found in on-disk bitmap after the last valid bit.
Checking internal tree..  

Bad root block 0. (--rebuild-tree did not complete)

Aborted
[root@arch ~]#

Ideas?

Thank you.

agkbill

Member

Registered: 2011-06-13

Posts: 85

Re: [SOLVED] rtorrent. Caught Bus error dumping stack.

Maybe the hard drive is OK.

The idea to use reiserfs was that I read that it is very good at handling small files, and torrents is about a lot of small files.

Well I copied all data I wanted to keep and made a ext3 file system.

Then fsck.ext3, looks ok as far as I know.

[root@arch ~]# fsck.ext3 /dev/sdb1
e2fsck 1.41.14 (22-Dec-2010)
/dev/sdb1: clean, 11/5005312 files, 360186/20010368 blocks
[root@arch ~]# fsck.ext3 -c /dev/sdb1
e2fsck 1.41.14 (22-Dec-2010)
Checking for bad blocks (read-only test): done                                
/dev/sdb1: Updating bad block inode.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

/dev/sdb1: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sdb1: 11/5005312 files (0.0% non-contiguous), 360186/20010368 blocks
[root@arch ~]#

MoonSwan

Member

From: Great White North

Registered: 2008-01-23

Posts: 881

Re: [SOLVED] rtorrent. Caught Bus error dumping stack.

If your drive supports SmartMonitoring you can install such a tool from pacman.  It is pretty reliable at telling you if your drive is failing or in good health.  You can also look to the manufacturer's website for any drive specific tools you can download and use to find out more info about the drive.  These are usually made as distributed ISO or floppy images in my experience.

agkbill

Member

Registered: 2011-06-13

Posts: 85

Re: [SOLVED] rtorrent. Caught Bus error dumping stack.

Thank you MoonSwan, I will look into "SmartMonitoring".

I have started rtorrent from scratch and loaded only one torrent that is running.
So far so good.

I found that people have experienced this kind of problem when hashing large files, that was exactly what was going on when I run into this.

To early to say if that is the problem for me.

agkbill

Member

Registered: 2011-06-13

Posts: 85

Re: [SOLVED] rtorrent. Caught Bus error dumping stack.

It looks like this problem have nothing to do with rtorrent.

At http://ubuntuforums.org/showthread.php?p=7449011 I could read:

Re: rtorrent - hash check and bad chunks
According to the author of the software it has to do with the file system.

It is a 3 year old issue with no solution.

http://libtorrent.rakshasa.no/ticket/483

I tried running rtorrent with the new ext3 file system that looked OK, but as soon as I tried to hash large files rtorrent failed.

With the knowledge that the author of rtorrent associate this with file systems I changed to reiserfs.

Now rtorrent have been running without problem and I have hashed larged files a number of times without problems.

Another solution that was mention in http://libtorrent.rakshasa.no/ticket/483 was:

I had the same problem. My solution is here. {{{ #max_open_files = 128 max_open_files = 64 }}} And then, i have never seen the problem. I hope this will help someone else. QNAP-119 3.2.5 Build 0409T rtorrent 0.8.6-1

This works for me as well.

I have not tried this, simply because so far the swap to reiserfs have worked.

All the best,

/Christer