Bug 1033356

Summary: when /boot is changed to btrfs, btrfs volume is improperly resized and is too small for installation
Product: [Fedora] Fedora Reporter: Chris Murphy <bugzilla>
Component: python-blivetAssignee: David Lehman <dlehman>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: amulhern, anaconda-maint-list, bcl, dlehman, g.kaviyarasu, jonathan, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-blivet-0.28-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1052439 (view as bug list) Environment:
Last Closed: 2014-12-02 19:14:25 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 1052439    
Attachments:
Description Flags
anaconda.log
none
program.log
none
storage.log none

Description Chris Murphy 2013-11-21 23:00:50 UTC
Description of problem:

In Manual Partitioning, after clicking on "automatically create" partitions, and changing /boot on ext4 to be /boot on BTRFS, the installer changes the existing ~442GB btrfs volume to a size of 2GB.

Version-Release number of selected component (if applicable):
anaconda-20.25.8-1.fc20

How reproducible:
Always

Steps to Reproduce:
1. Manual partitioning
2. Automatically create partitions
3. Click on /boot and change device type to BTRFS, click update

Actual results:
All mountpoints on the BTRFS volume change size to ~2GB.

Expected results:
Established size of the volume shouldn't change.

Additional info:

Comment 1 Chris Murphy 2013-11-21 23:01:41 UTC
Created attachment 827499 [details]
anaconda.log

Comment 2 Chris Murphy 2013-11-21 23:01:57 UTC
Created attachment 827500 [details]
program.log

Comment 3 Chris Murphy 2013-11-21 23:02:14 UTC
Created attachment 827501 [details]
storage.log

Comment 4 David Lehman 2013-11-22 14:44:47 UTC
This is related to how we calculate the base size for the volume when adding a subvolume in combination with how the automatic partitioning requests are defined (they have small base sizes).