libreport version: 2.0.6 executable: /usr/bin/python hashmarkername: anaconda kernel: 3.1.0-7.fc16.i686 product: Fedora reason: RuntimeError: error copying filesystem! time: Sat Nov 12 11:05:50 2011 version: 16 description: :The following was filed automatically by anaconda: :anaconda 16.25 exception report :Traceback (most recent call first): : File "/usr/lib/python2.7/site-packages/pyanaconda/livecd.py", line 181, in doInstall : raise RuntimeError, "error copying filesystem!" : File "/usr/lib/python2.7/site-packages/pyanaconda/backend.py", line 205, in doInstall : return anaconda.backend.doInstall(anaconda) : File "/usr/lib/python2.7/site-packages/pyanaconda/dispatch.py", line 373, in dispatch : self.dir = self.steps[self.step].target(self.anaconda) : File "/usr/lib/python2.7/site-packages/pyanaconda/dispatch.py", line 241, in go_forward : self.dispatch() : File "/usr/lib/python2.7/site-packages/pyanaconda/gui.py", line 1201, in nextClicked : self.anaconda.dispatch.go_forward() : File "/usr/lib/python2.7/site-packages/pyanaconda/iw/progress_gui.py", line 79, in renderCallback : self.intf.icw.nextClicked() : File "/usr/lib/python2.7/site-packages/pyanaconda/gui.py", line 1221, in handleRenderCallback : self.currentWindow.renderCallback() :RuntimeError: error copying filesystem!
Created attachment 533224 [details] abrt.log abrt.log
Created attachment 533225 [details] anaconda.log
Created attachment 533229 [details] /var/log/messages
Live System "Transfer to disk" failed apparently due to filesystem size problems The /dev/sdc disk used was partitionned and reformated with Anaconda installer But resulting filesystem size is apparently smaller than the partition fdisk reports 3918848K for /dev/sdc2 df reports only 2347616K for the fs created on top of partition /dev/sdc2. # fdisk -l /dev/sdc Disk /dev/sdc: 4016 MB, 4016046080 bytes 124 heads, 62 sectors/track, 1020 cylinders, total 7843840 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: 0x0002355f Device Boot Start End Blocks Id System /dev/sdc1 2048 6143 2048 83 Linux /dev/sdc2 * 6144 7843839 3918848 83 Linux # df -k /media/sdc2 Filesystem 1K-blocks Used Available Use% Mounted on /dev/sdc2 2347616 2306988 16768 100% /media/sdc2
Created attachment 533230 [details] Anaconda exception report
resize2fs of Anaconda partitionned fs allow the fs to grow to 3857104 # resize2fs /dev/sdc2 resize2fs 1.41.14 (22-Dec-2010) Resizing the filesystem on /dev/sdc2 to 979712 (4k) blocks. The filesystem on /dev/sdc2 is now 979712 blocks long. # df -k /media/sdc2 Filesystem 1K-blocks Used Available Use% Mounted on /dev/sdc2 3857104 2309028 1508900 61% /media/sdc2
Tried to recreate within "Install to harddrive" this 3827MB partition. Using this time the "Fixed size" 3827MB option, instead of the "Fill to maximum allowable size" as it was done previously. It didn't make a differance. The fs created by Anaconda afterwards, still has size: 2293MB < 3827MB (the partition size).
if you try instead the Fedora installer with the options "Use All Space" or "Existing Linux System(s)". The installer outputs an error :"Partition / is less than 2330MB". This error message is printed although the disk size is 3830MB with prexisting : 2MB /dev/sdc1 "BIOS Boot" and 3827MB "ext4" partitions. The following errors occurred with your partitioning: Your / partition is less than 2330.0 MB which is lower than recommended for a normal Fedora Live install. you have not created a bootloader stage1 target device This can happen if there is not enough space on your hard drive(s) for the installation. Press 'OK' to choose a different partitioning option.
According to the anaconda exception report it ran out of space to write the image. copied: 4009754624 size: 2443182080.0 It also appears to have written more than it should have. How did you create your install media? Is it an iso or USB? Did you do anything in the live system before running the install?
Ok, I can reproduce this. I think this is because we are now using a squashfs.img as the root filesystem the minimum size calculation for Live is incorrect. It needs to be at least 4096MB for the copy to work. The size discrepancy you are seeing is because it copies the disk image over to the target first, which results in the filesystem size being the same as the source. It will then resize it to match the size of the partition.
To create the install media, I used a USB key and the program liveusb-creator-3.11.6-setup.exe. The size of the USB key is 4016 MB, 4016046080 bytes. I used a second identical 4GB USB key as a target for the "Install to harddrive". I understand that my 4G USB Key is now too small with FC16, although it was not too small with FC15 using the same install procedure. One message is misleading though with the installer. When you use the "Use All Space" or "Existing Linux System(s)" options. It tells you : "Your / partition is less than 2330.0 MB which is lower than recommended for a normal Fedora Live install." It's hard to correlate this message to the 4GB USB key size which is about double the 2330MB mentioned in the error message.
Thanks for the additional info. The problem lies with how Live handles the install. It copies the source filesystem, byte-for-byte to the target before resizing. So even if < 4G is being used it needs that much space for the copy. You should still be able to install Fedora to your 4G USB key using the normal install media (DVD or netboot) which don't have this limitation, although the minimum size will depend on the package selection that you make.
I think the requirement may differ for some spins: [adamw@adam spin-kickstarts (F-16 %)]$ grep "\-\-size" * fedora-aos.ks:part / --size 1024 --fstype ext4 --ondisk sda fedora-install-fedora.ks:#part iso --size=4998 fedora-live-base.ks:part / --size 3072 --fstype ext4 fedora-livecd-soas.ks:part / --size=2048 fedora-live-desktop.ks:part / --size 4096 fedora-livedvd-electronic-lab.ks:part / --size=8192 fedora-livedvd-games.ks:part / --size 10240 fedora-livedvd-robotics.ks:part / --size 10240 fedora-livedvd-scientific-kde.ks:part / --size 10000 fedora-live-kde.ks:part / --size=8192 fedora-live-mini.ks:part / --size 4096 --fstype ext4 fedora-virt-server.ks.in:part / --size=550 --grow --fstype=ext4 that defines the squashfs size, right? So we could say that the minimum is 3072MiB for most spins (that's what's in live-base.ks), for SoaS it's 2048MiB... (note that 8192MiB for KDE is for the bigger-than-a-CD-size spin, which we don't build or ship by default. The shipped KDE spin is fedora-livecd-kde.ks, which has the 3072MiB size). -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Adam, that's correct. I'll sort out how to grab the underlying size and get this fixed for F17.
I got the same problem installing a live Fedora 16 64-bit w/ GNOME to a 4016 MB partition using a custom layout. So, I installed a live Fedora 16 64-bit w/ SOAS to that partition just fine. I can get to a terminal and root mode, so have done "yum update" and other commands. Now, how do I change the display manager to GNOME from SOAS?
yum install @gnome-desktop yum install switchdesk yum install switchdesk-gui switchdesk After a reboot, during the login process, I can pick either GNOME or Sugar(SOAS) as my desktop. This method ended up with less disk space used than either Fedora Core 14 or 15 w/ GNOME (the default Live system to download).
*** Bug 767660 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. 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 '16'. 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 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 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 to click on "Clone This Bug" and open it against that version of Fedora. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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. Thank you for reporting this bug and we are sorry it could not be fixed.