Description of problem: Version-Release number of selected component: anaconda-18.6.4-1.fc18.x86_64 Additional info: libreport version: 2.0.12 cmdline: initrd=initrd0.img root=live:CDLABEL=Fedora-18-Alpha-TC5-x86_64-Live- rootfstype=auto ro rd.live.image quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 BOOT_IMAGE=vmlinuz0 kernel: 3.6.0-0.rc2.git2.1.fc18.x86_64
Created attachment 608859 [details] File: ifcfg.log
Created attachment 608860 [details] File: anaconda-tb
Created attachment 608861 [details] File: environ
Created attachment 608862 [details] File: type
Created attachment 608863 [details] File: storage.log
Created attachment 608864 [details] File: other involved packages
Created attachment 608865 [details] File: program.log
Created attachment 608866 [details] File: product
Created attachment 608867 [details] File: anaconda.log
Created attachment 608868 [details] File: hashmarkername
Created attachment 608869 [details] File: version
Created attachment 608870 [details] File: release
Created attachment 608871 [details] File: messages
Created attachment 608872 [details] File: description
According to the rsync man page: 12 Error in rsync protocol data stream
Please describe steps to reproduce.
I have not seen this again. I have not seen this after it was possible to use USB to install.
The attached anaconda-tb shows rsync failing with code 12 while copying files to a 500 MiB partition (sdb13 mounted on /mnt/sysimage). rsync did not log any error messages about running out of disk space, but that appears to be what happened. Why wouldn't rsync log informative error messages when it runs out of disk space on the destination? [snippets from /tmp/program.log in attached anaconda-tb] ... 14:42:21,889 INFO program: Running... mke2fs -t ext4 /dev/sdb13 ... 14:42:22,143 INFO program: Block size=1024 (log=0) ... 14:42:22,147 INFO program: 128016 inodes, 512000 blocks ... 14:42:23,279 INFO program: Running... /bin/mount -n -t ext4 -o defaults /dev/sdb13 /mnt/sysimage ... 14:42:23,813 INFO program: Running... rsync -rlptgoDHAXvx / /mnt/sysimage ... 14:44:28,067 INFO program: usr/lib/python2.7/site-packages/cloudfiles/storage_object.py 14:44:28,484 ERR program: rsync: writefd_unbuffered failed to write 4 bytes to socket [sender]: Broken pipe (32) 14:44:28,586 ERR program: rsync: connection unexpectedly closed (185645 bytes received so far) [sender] 14:44:28,588 ERR program: rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] ...
(In reply to comment #18) > The attached anaconda-tb shows rsync failing with code 12 while copying > files to a 500 MiB partition (sdb13 mounted on /mnt/sysimage). ... Why is anaconda trying to install to a 500 MiB partition?
Anaconda checks for sufficient space before making partitions, then creates a swap equal to 2x physical size. Auto partitioning a 8GB disk with 2GB RAM creates a 4GB swap + 500M boot + 3.5GB root, which is indeed, now insufficient.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.