Version-Release number of selected component: rdiff-backup-2.2.5-2.fc38 Additional info: reporter: libreport-2.17.11 kernel: 6.3.8-200.fc38.x86_64 package: rdiff-backup-2.2.5-2.fc38 cmdline: /usr/bin/python3 /usr/bin/rdiff-backup -v4 backup --exclude /home/jan/Downloads --exclude /home/jan/.VirtualBox/Machines --exclude /tmp --exclude /mnt --exclude /proc --exclude /backup/externalHDD --exclude /media --exclude /lib --exclude /lib64 --exclude /bin --exclude /dev --exclude /lost+found --exclude /misc --exclude /net --exclude /opt --exclude /sbin --exclude /selinux --exclude /srv --exclude /usr --exclude /var --exclude /sys --exclude /iso --exclude /media/Backup --exclude /run/media --exclude /home/jan/.bitcoin/blocks --exclude /home/jan/.bitcoin/chainstate --exclude /run --exclude /var/run / /run/media/jan/BackupX/rdiff_backup_nyx_0 executable: /usr/bin/rdiff-backup reason: rpath.py:1548:copyfileobj:OSError: [Errno 28] No space left on device exception_type: OSError type: Python3 crash_function: copyfileobj uid: 0 interpreter: python3-3.11.3-2.fc38.x86_64 runlevel: N 5 Truncated backtrace: #1 [/usr/lib64/python3.11/site-packages/rdiff_backup/rpath.py:1548] copyfileobj #2 [/usr/lib64/python3.11/site-packages/rdiff_backup/rpath.py:1152] write_from_fileobj #3 [/usr/lib64/python3.11/site-packages/rdiff_backup/rpath.py:1620] copy_reg_file #4 [/usr/lib64/python3.11/site-packages/rdiff_backup/rpath.py:1586] copy #5 [/usr/lib64/python3.11/site-packages/rdiff_backup/robust.py:94] check_common_error #6 [/usr/lib64/python3.11/site-packages/rdiff_backup/backup.py:701] _patch_snapshot_to_temp #7 [/usr/lib64/python3.11/site-packages/rdiff_backup/backup.py:655] _patch_to_temp #8 [/usr/lib64/python3.11/site-packages/rdiff_backup/backup.py:802] fast_process_file #9 [/usr/lib64/python3.11/site-packages/rdiff_backup/rorpiter.py:146] __call__ #10 [/usr/lib64/python3.11/site-packages/rdiff_backup/backup.py:210] patch_and_increment #11 [/usr/lib64/python3.11/site-packages/rdiff_backup/backup.py:53] mirror_and_increment_compat200 #12 [/usr/lib64/python3.11/site-packages/rdiffbackup/actions/backup.py:154] run #13 [/usr/lib64/python3.11/site-packages/rdiffbackup/run.py:110] main_run #14 [/usr/lib64/python3.11/site-packages/rdiffbackup/run.py:37] main #15 [/usr/bin/rdiff-backup:33] <module>
Created attachment 1974496 [details] File: mountinfo
Created attachment 1974497 [details] File: cpuinfo
Created attachment 1974498 [details] File: backtrace
Created attachment 1974499 [details] File: open_fds
Created attachment 1974500 [details] File: os_info
Created attachment 1974501 [details] File: cgroup
Created attachment 1974502 [details] File: environ
Created attachment 1974503 [details] File: namespaces
@jan.public The failure reason was "OSError: [Errno 28] No space left on device". Is there some other issue that needs to be looked into for this, or should this be closed?
Disk was indeed full, but should ABRT trigger on this? If that is ok, feel free to close this issue.
I think that ABRT just triggers on the fact rdiff-backup generates a stack-trace. It doesn't care what is the cause. On the other hand rdiff-backup believes that the failure is important enough to indicate what may have caused the issue and doesn't currently distinguish between OS caused errors. Maybe in future, but currently it is more important to get the code solid.