The following was filed automatically by anaconda: anaconda 15.30 exception report Traceback (most recent call first): File "/usr/lib/python2.7/site-packages/pyanaconda/storage/formats/fs.py", line 372, in doFormat raise FormatCreateError("format failed: %s" % ret.rc, self.device) File "/usr/lib/python2.7/site-packages/pyanaconda/storage/formats/fs.py", line 848, in create return self.doFormat(*args, **kwargs) File "/usr/lib/python2.7/site-packages/pyanaconda/storage/deviceaction.py", line 428, in execute options=self.device.formatArgs) File "/usr/lib/python2.7/site-packages/pyanaconda/storage/devicetree.py", line 313, in processActions action.execute(intf=self.intf) File "/usr/lib/python2.7/site-packages/pyanaconda/storage/__init__.py", line 356, in doIt self.devicetree.processActions() File "/usr/lib/python2.7/site-packages/pyanaconda/packages.py", line 116, in turnOnFilesystems anaconda.storage.doIt() File "/usr/lib/python2.7/site-packages/pyanaconda/dispatch.py", line 211, in moveStep rc = stepFunc(self.anaconda) File "/usr/lib/python2.7/site-packages/pyanaconda/dispatch.py", line 130, in gotoNext self.moveStep() File "/usr/lib/python2.7/site-packages/pyanaconda/gui.py", line 1257, in nextClicked self.anaconda.dispatch.gotoNext() FormatCreateError: ('format failed: 1', '/dev/mapper/vg_kralik-LogVol01')
Created attachment 497321 [details] Attached traceback automatically from anaconda.
Created attachment 497325 [details] Attached traceback automatically from anaconda.
I think this issue is caused by creating btrfs partition. The second report was caused by using default disk layout at first, but shrinking root partition and creating another 100MB btrfs LV partition (mounted at /opt) in the same volume group. Anaconda CCed me again to this bug, so I believe it is also the root cause of the first failure. In case it is really caused by creating btrfs partition, I'm marking this bug as F15Blocker according to this release criterion: "5. The installer must be able to create and install to any workable partition layout using any file system offered in a default installer configuration, LVM, software, hardware or BIOS RAID, or combination of the above" https://fedoraproject.org/wiki/Fedora_15_Final_Release_Criteria
From the logs: Running... mkfs.btrfs /dev/mapper/VolGroup-LogVol02 device /dev/mapper/VolGroup-LogVol02 is too small (must be at least 256 MB) So the minimum device size for a btrfs filesystem is 256 MB. In the short term, you can just make sure your device is large enough. In the longer term, we can update the minimum for btrfs in anaconda very easily.
After discussion in #anaconda, it seems the problem here is that the btrfs filesystem has a minimum size of 256M, and anaconda isn't enforcing that minimum partition size. 09:49:02 wwoods: no, there's totally a _minSize attribute for filesystems 09:49:08 wwoods: it's just not set for btrfs 09:49:20 wwoods: dlehman: we talked about this yesterday actually 09:50:05 dlehman: wwoods: yeah, oddly enough 09:50:17 wwoods: minsize is 256MiB, maxsize is 16EiB (1EiB = 1024PiB = 1024*1024TiB = HOOOORJJJ THAT'S A LOT OF DATA) According to dlehman, support exists for anaconda to enforce this, but the MINSIZE is currently not set. The fix is a one-liner, and should be reasonable for F15. While this feels like a documentable edge condition, it certainly is covered by the final criteria "The installer must be able to create and install to any workable partition layout using any file system offered in a default installer configuration, LVM, software, hardware or BIOS RAID, or combination of the above " +1 Blocker, +1 NTH (if needed)
I can confirm that creating btrfs partition larger than 256MB seems to be working ok.
Should be fixed in anaconda-15.31-1.
Discussed in the 2011-05-06 blocker review meeting. Accepted as F15 final blocker under the following criteria: "The installer must be able to create and install to any workable partition layout using any file system offered in a default installer configuration, LVM, software, hardware or BIOS RAID, or combination of the above "
anaconda-15.31-1.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/anaconda-15.31-1.fc15
Package anaconda-15.31-1.fc15: * should fix your issue, * was pushed to the Fedora 15 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing anaconda-15.31-1.fc15' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/anaconda-15.31-1.fc15 then log in and leave karma (feedback).
VERIFIED this fix using a custom boot.iso built with anaconda-15.31-1.fc15. Anaconda provides an error dialog noting that the requested size is too small. The user is able to continue and readjust the partition size as directed.
anaconda-15.31-1.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.