Bug 643907

Summary:	fsadm does not know about btrfs
Product:	[Fedora] Fedora	Reporter:	Zdenek Kabelac <zkabelac>
Component:	lvm2	Assignee:	Ondrej Kozina <okozina>
Status:	ASSIGNED ---	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	rawhide	CC:	agk, anotherjonathon, bmarzins, bmr, dwysocha, heinzm, jonathan, lvm-team, msnitzer, prajnoha
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Zdenek Kabelac 2010-10-18 13:46:17 UTC

Description of problem:

btrfs is not supported filesystem by fsadm tool.

btrfscl from btrfs-progs could be used for fs resize.

Version-Release number of selected component (if applicable):
lvm2-2.02.74-2.fc15.x86_64

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Ric Wheeler 2010-10-18 13:53:59 UTC

Is there any reason to use this tool for btrfs? Btrfs tools can do this all without any help (it is a one step process) so wrapping them inside of fsadm would be a needless complication I suspect.

Thanks!

Comment 2 Zdenek Kabelac 2010-10-18 14:05:35 UTC

There could be some users - who will use btrfs over LV device - and they might expect that 'lvresize -r' will resize btrfs on this LV partition. I'm not saying it would be common use-case, but implementing this feature into fsadm isn't a bit problem.

Comment 3 Ric Wheeler 2010-10-18 14:10:26 UTC

Thanks - that does make sense...

Comment 4 Fedora End Of Life 2013-04-03 20:11:03 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19