Bug 571526 - [abrt] crash in rdiff-backup-1.2.8-3.fc12: rpath.py:260:rename:OSError: [Errno 28] No space left on device
Summary: [abrt] crash in rdiff-backup-1.2.8-3.fc12: rpath.py:260:rename:OSError: [Errn...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: rdiff-backup
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Kevin Fenzi
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:970d4f56
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-08 18:53 UTC by Zach
Modified: 2010-03-09 17:15 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-03-09 17:15:54 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (1.70 KB, text/plain)
2010-03-08 18:53 UTC, Zach
no flags Details

Description Zach 2010-03-08 18:53:13 UTC
abrt 1.0.7 detected a crash.

architecture: x86_64
cmdline: /usr/bin/python /usr/bin/rdiff-backup -v3 --exclude-sockets --no-hard-links /home/Zach/Documents /media/LINUXBACKUP_/Backups/COMPUTER-rdiff-backup-home/
comment: I can see the Error No space left on device, but there is space remaining on the harddrive.
component: rdiff-backup
executable: /usr/bin/rdiff-backup
kernel: 2.6.32.9-67.fc12.x86_64
package: rdiff-backup-1.2.8-3.fc12
reason: rpath.py:260:rename:OSError: [Errno 28] No space left on device
release: Fedora release 12 (Constantine)

backtrace
-----
rpath.py:260:rename:OSError: [Errno 28] No space left on device

Traceback (most recent call last):
  File "/usr/bin/rdiff-backup", line 30, in <module>
    rdiff_backup.Main.error_check_Main(sys.argv[1:])
  File "/usr/lib64/python2.6/site-packages/rdiff_backup/Main.py", line 304, in error_check_Main
    try: Main(arglist)
  File "/usr/lib64/python2.6/site-packages/rdiff_backup/Main.py", line 324, in Main
    take_action(rps)
  File "/usr/lib64/python2.6/site-packages/rdiff_backup/Main.py", line 280, in take_action
    elif action == "backup": Backup(rps[0], rps[1])
  File "/usr/lib64/python2.6/site-packages/rdiff_backup/Main.py", line 346, in Backup
    backup.Mirror(rpin, rpout)
  File "/usr/lib64/python2.6/site-packages/rdiff_backup/backup.py", line 38, in Mirror
    DestS.patch(dest_rpath, source_diffiter)
  File "/usr/lib64/python2.6/site-packages/rdiff_backup/backup.py", line 232, in patch
    ITR(diff.index, diff)
  File "/usr/lib64/python2.6/site-packages/rdiff_backup/rorpiter.py", line 281, in __call__
    last_branch.fast_process(*args)
  File "/usr/lib64/python2.6/site-packages/rdiff_backup/backup.py", line 532, in fast_process
    (tf, mirror_rp)) is None:
  File "/usr/lib64/python2.6/site-packages/rdiff_backup/robust.py", line 32, in check_common_error
    try: return function(*args)
  File "/usr/lib64/python2.6/site-packages/rdiff_backup/rpath.py", line 260, in rename
    rp_source.conn.os.rename(rp_source.path, rp_dest.path)
OSError: [Errno 28] No space left on device

Local variables in innermost frame:
rp_source: <rdiff_backup.FilenameMapping.QuotedRPath instance at 0x16aaab8>
rp_dest: <rdiff_backup.FilenameMapping.QuotedRPath instance at 0x1696b00>
error: OSError(28, 'No space left on device')

How to reproduce
-----
1.Trying to backup to External Harddrive
2.
3.

Comment 1 Zach 2010-03-08 18:53:15 UTC
Created attachment 398583 [details]
File: backtrace

Comment 2 Kevin Fenzi 2010-03-08 19:04:30 UTC
The No space left on device is an OS error that python is returning to us. 

Can you provide: 

df 
and
df -i

output please? 

Any errors from the drive in 'dmesg' ?

Comment 3 Zach 2010-03-08 21:12:13 UTC
In reply to comment #2)
> The No space left on device is an OS error that python is returning to us. 
> 
> Can you provide: 
> 
> df 

@wavetrain log]$ df
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/sda3             25196892   5189460  19751516  21% /
tmpfs                  1803212      1712   1801500   1% /dev/shm
/dev/sda2               247919     71645    163474  31% /boot
/dev/sda7            421935660  91074472 309428052  23% /home
/dev/sda6              4031676   1762264   2064616  47% /var
/dev/sdb2            210511412  60286060 150225352  29% /media/Time Machine
/dev/sdb1            277807264   7194944 270612320   3% /media/LINUXBACKUP_
AFS                    9000000         0   9000000   0% /afs


> and
> df -i

@wavetrain log]$ df -i
Filesystem            Inodes   IUsed   IFree IUse% Mounted on
/dev/sda3            1605632  201460 1404172   13% /
tmpfs                 450803       8  450795    1% /dev/shm
/dev/sda2              64000      47   63953    1% /boot
/dev/sda7            26796032  288378 26507654    2% /home
/dev/sda6             256000   17005  238995    7% /var
/dev/sdb2            4294967295  727310 4294239985    1% /media/Time Machine
/dev/sdb1                  0       0       0    -  /media/LINUXBACKUP_
AFS                  9000000       0 9000000    0% /afs


The backup drive is /media/LINUXBACKUP_

> 
> output please? 
> 
> Any errors from the drive in 'dmesg' ?    

I'm not entirely certain what I should look for in 'dmesg' but I've included the final portion of 'dmesg'. When I 'dmesg|grep sdb1', I get  

sdb: sdb1 sdb2 

'dmesg'

------------[ cut here ]------------
WARNING: at fs/fs-writeback.c:1112 __mark_inode_dirty+0xef/0x12f()
Hardware name: Dell DXP051                  
Modules linked in: libafs(P) vfat fat nls_utf8 hfsplus fuse vboxnetadp vboxnetflt vboxdrv p4_clockmod freq_table speedstep_lib nf_conntrack_netbios_ns ip6t_REJECT nf_conntrack_ipv6 ip6table_filter ip6_tables ipv6 uinput snd_hda_codec_idt snd_hda_intel snd_hda_codec snd_hwdep snd_seq snd_seq_device snd_pcm snd_timer nvidia(P) snd dcdbas i2c_i801 i2c_core soundcore iTCO_wdt iTCO_vendor_support serio_raw e1000e snd_page_alloc usb_storage dm_multipath [last unloaded: freq_table]
Pid: 4764, comm: man Tainted: P        W  2.6.32.9-67.fc12.x86_64 #1
Call Trace:
 [<ffffffff81056348>] warn_slowpath_common+0x7c/0x94
 [<ffffffff81056374>] warn_slowpath_null+0x14/0x16
 [<ffffffff8113a1ee>] __mark_inode_dirty+0xef/0x12f
 [<ffffffff8112fdbd>] touch_atime+0x107/0x12a
 [<ffffffff8112af05>] ? filldir+0x0/0xc4
 [<ffffffff8112b13a>] vfs_readdir+0x8d/0xb4
 [<ffffffff8112b2aa>] sys_getdents+0x81/0xd1
 [<ffffffff81011d32>] system_call_fastpath+0x16/0x1b
---[ end trace 3839f2be88f9a108 ]---

Comment 4 Kevin Fenzi 2010-03-08 21:58:36 UTC
what filesystem type?

That does seem like a filesystem error to me. I would suggest booting from a rescue media and running a fsck on the indicated volume and confirm it's coming up clean. Then see if a backup runs correctly.

Comment 5 Zach 2010-03-09 14:52:26 UTC
I ended up reformatting the external drive and was able to complete a successful backup. It seems the drive was originally fat32, and I formatted the drive to ext4. Probably something I should have tried before posting, but thanks for the insight and help.

Comment 6 Kevin Fenzi 2010-03-09 17:15:54 UTC
Excellent. Will go ahead and close this then. 

Feel free to reopen or file a new bug if you spot anything further.


Note You need to log in before you can comment on or make changes to this bug.