Bug 1303006

Summary:	Incorrect minimum size reported
Product:	[Fedora] Fedora	Reporter:	Vratislav Podzimek <vpodzime>
Component:	btrfs-progs	Assignee:	Josef Bacik <josef>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	24	CC:	bugzilla, esandeen, josef, mmahut
Target Milestone:	---	Keywords:	Reopened
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-08 12:43:11 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:
Embargoed:

Description Vratislav Podzimek 2016-01-29 09:37:56 UTC

Description of problem:
When trying to create a new btrfs volume on devices with minimum size, 'mkfs.btrfs' reports "exit code 256: not enough free space". I interpreted the minimum size requirement given by 'mkfs.btrfs' as being in bytes (see bug #1302997) which gives 40 MiB. However, even 120 MiB is not enough. 128 MiB works, but that's quite a different value!

Version-Release number of selected component (if applicable):
btrfs-progs-4.3.1-1.fc23.x86_64

How reproducible:
100 %

Steps to Reproduce:
1. run mkfs.btrfs on block devices with minimum size reported by mkfs.btrfs itself (probably 40 MiB)

Actual results:
exit code 256: not enough free space

Expected results:
a new btrfs volume successfully created

Comment 1 Fedora End Of Life 2016-11-24 15:15:59 UTC

This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. 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 EOL if it remains open with a Fedora  'version'
of '23'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 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  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

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.

Comment 2 Fedora End Of Life 2016-12-20 18:17:12 UTC

Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 3 Vratislav Podzimek 2017-01-17 07:24:46 UTC

This is still the same on F24

Comment 4 Eric Sandeen 2017-01-17 14:50:07 UTC

Please report these bugs to the upstream list - it will need to be fixed upstream before it can be fixed in Fedora.  If upstream ignores it, then it won't get fixed in Fedora.

Judging from https://bugzilla.kernel.org/show_bug.cgi?id=112461 filed a year ago and ignored since, it seems that upstream may not be interested in resolving this bug.

Comment 5 Fedora End Of Life 2017-07-25 19:51:52 UTC

This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. 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 EOL if it remains open with a Fedora  'version'
of '24'.

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.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 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  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

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.

Comment 6 Fedora End Of Life 2017-08-08 12:43:11 UTC

Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.