Bug 798750 - BTRFS crashes in Anaconda when selected as /boot partition
Summary: BTRFS crashes in Anaconda when selected as /boot partition
Keywords:
Status: CLOSED DUPLICATE of bug 787341
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 17
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-29 18:27 UTC by Max E
Modified: 2012-02-29 20:27 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-29 20:27:41 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Max E 2012-02-29 18:27:58 UTC
Description of problem:

currently running F17-alpha, and tried to do a manual partition.  Selected as a filing system on disk partitioning tool [manually setting up virtual machine] and anaconda crashed.  This system is running under Virtualbox 4.1.8

Version-Release number of selected component (if applicable):

Fedora 17 Alpha

How reproducible:

Everytime

Steps to Reproduce:
1. Selected Basic Storage Type
2. Initialised disk
3. named machine f17-tester
4. sorted out the root password
5. Selected Create custom Layout
6. Create Standard Partition
7. selected mount point: /boot
8. selected file system type: btrfs
9. selected size: 500M
10. CRASHED!
11. Pressed DEBUG and Anaconda crashed out to command
  
Actual results:

Anaconda crashes out

Expected results:

Either accept btrfs can be used for /boot or not....

Additional info:

The only thing I could get out was: btrfs_dev=self.storage.devicetree.getChildren(device)[0]

Comment 1 Max E 2012-02-29 18:29:37 UTC
sorry - additional error statement:

/usr/lib64/python2.7/site-packages/pyanaconda/iw/partition_gui.py(946)addDevice()

and crashed out to 

(Pdb) prompt

Comment 2 Chris Lumens 2012-02-29 20:27:41 UTC

*** This bug has been marked as a duplicate of bug 787341 ***


Note You need to log in before you can comment on or make changes to this bug.