The following was filed automatically by anaconda: anaconda 11.5.0.47 exception report Traceback (most recent call first): File "/usr/lib/anaconda/iw/partition_gui.py", line 1122, in editPartition raise RuntimeError, ("Returning partitions to state " File "/usr/lib/anaconda/iw/partition_gui.py", line 1068, in editCB self.editPartition(device) File "/usr/lib/anaconda/iw/partition_gui.py", line 943, in treeActivateCB self.editCB() RuntimeError: Returning partitions to state prior to edit failed
Created attachment 341583 [details] Attached traceback automatically from anaconda.
What I did: I started with both drives empty, only with MSDOS partition table. I selected automatic layout and opted to modify. I removed VGs. I changed PV on second drive into 8GB partition, mount on /, type btrfs, selected sda and sdb as allowable drives and 8192MB as fixed size. Then I edited PV on first drive with exact sam information (/, btrfs, both drives, 8192 fixed). At this point I got exception. What was expected: I expected to have / with btrfs filesystem spanning over sda2 and sdb1. I also expected question if I want RAID0 or RAID1 withing btrfs over those partitions.
Thanks for the report. (In reply to comment #2) > What was expected: > I expected to have / with btrfs filesystem spanning over sda2 and sdb1. I also > expected question if I want RAID0 or RAID1 withing btrfs over those partitions. None of what you expected is going to work. We only support the creation of btrfs filesystems on a single block device, just like all other filesystems.
Created attachment 343913 [details] Attached traceback automatically from anaconda.
Created attachment 345979 [details] Attached traceback automatically from anaconda.
*** Bug 502092 has been marked as a duplicate of this bug. ***
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle. Changing version to '11'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
*** Bug 519212 has been marked as a duplicate of this bug. ***
*** Bug 519727 has been marked as a duplicate of this bug. ***
Created attachment 358893 [details] anaconda log from fedora11
Created attachment 358894 [details] F12 alpha: anaconda log file
Created attachment 360123 [details] Attached traceback automatically from anaconda.
Created attachment 362657 [details] anaconda log ------- Comment on attachment From pavan.naregundi.com 2009-09-25 06:58 EDT------- Still seeing this issue in latest rawhide with anaconda 12.26. RedHat, Any updates on this?
Can you please provide a detailed description of the process to reproduce this behavior?
I have had several instances of Bug 502092. Installing to a fresh machine but simply wanted to increase the size of /boot from 200MB to 1000. This fails saying there is not enough free space, but instead of allowing me to reduce the other partition/vg, it crashes. HP DL 380 G4 with 2 300GB hot plug SCA scsi drives in a mirror.
*** Bug 526573 has been marked as a duplicate of this bug. ***
------- Comment From pavan.naregundi.com 2009-10-05 02:19 EDT------- (In reply to comment #21) > Can you please provide a detailed description of the process to reproduce this > behavior? > One of the way to reproduce this bug, Steps: 1. Start f12 rawhide installation with vnc 2. Select "Use entire drive" in partitioning. This option should not leave any free space on the disk. * Also check for review and modify partitioning layout * Pressing next should be able to partition information. 3. Select one the partition and press 'Edit' 4. Increase the size of the partition and press OK. * This should give an error of saying " not enough free space on disk". Which is expected. 5. Now click on 'OK' for the error. This will crash the anaconda.
Listing as beta blocker, pretty annoying bug.
I'm getting sometimes this error when editing (and saving as is) partition when disk is full (tracebacks are in bug# 519212).
Unable to reproduce the problem when testing anaconda-12.35 + http://dlehman.fedorapeople.org/updates-498026.img.
Fixed in anaconda-12.36-1.
That anaconda has been tagged.
------- Comment From pavan.naregundi.com 2009-10-26 01:59 EDT------- Tested with F12 rawhide having anaconda 12.39. I confirm that the issue is fixed now. Thanks
Thanks for the feedback Pavan!
anaconda-12.39-1 failure (see anacdump.txt in attachment#366492 [details]) 1) First, do this - https://fedoraproject.org/wiki/QA/TestCases/PartitioningExt4OnNativeDevice 2) After that install, do this - https://fedoraproject.org/wiki/QA:Testcase_Anaconda_autopart_%28shrink%29_install 3) There will be 2 'PPCPReP Boot' Partitions, I clicked "EDIT" on the original partition and chose to format it again. Click OK Crash.
Well, either re-open this bug or file a new one? New comments on closed bugs have a tendency to get lost in the shuffle... -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Comment#25 opened as bug#531629