Bug 927174

Summary:	pool-build --overwrite can not format type xfs filesystem
Product:	[Community] Virtualization Tools	Reporter:	Huang Wenlong <whuang>
Component:	libvirt	Assignee:	Libvirt Maintainers <libvirt-maint>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	acathrow, cwei, dallan, dyuan, jtomko, mzhan
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	927172	Environment:
Last Closed:	2014-04-03 10:25:01 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:
Bug Depends On:	927172
Bug Blocks:

Description Huang Wenlong 2013-03-25 09:32:51 UTC

Reproduce it with libvirt-1.0.3-1.el7.x86_64
+++ This bug was initially created as a clone of Bug #927172 +++

Description of problem:
pool-build --overwrite   can not format type xfs filesystem

Version-Release number of selected component (if applicable):
libvirt-0.10.2-18.el6_4.2.x86_64

How reproducible:
100

Steps to Reproduce:
1. prepare a fs ext3 partition
<pool type='fs'>
  <name>sda2</name>
  <source>
    <device path='/dev/sda2'/>
    <format type='xfs'/>
  </source>
  <target>
    <path>/var/lib/libvirt/images/sda2</path>
    <permissions>
      <mode>0755</mode>
      <owner>0</owner>
      <group>0</group>
    </permissions>
  </target>
</pool>

2. format sda2
#mkfs.ext3 -F /dev/sda2

3. define and build pool --overwrite
# virsh pool-define sda2-new.xml
Pool sda2 defined from sda2-new.xml

## virsh pool-build --overwrite sda2
error: Failed to build pool sda2
error: Failed to make filesystem of type 'xfs' on device '/dev/sda2': File exists


 
Actual results:
as steps

Expected results:
pool-build should succeed

Additional info:
GFS2 format also can not be formated via pool-build --overwrite

Comment 2 Ján Tomko 2014-04-03 10:25:01 UTC


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