Bug 840572

Summary: virt-make-fs / tar-in should support vfat properly
Product: [Community] Virtualization Tools Reporter: Richard W.M. Jones <rjones>
Component: libguestfsAssignee: Richard W.M. Jones <rjones>
Status: CLOSED UPSTREAM QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: dyasny, mbooth
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-07-18 12:10:26 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 Richard W.M. Jones 2012-07-16 15:37:50 UTC 
Description of problem:

At the moment if you try to use 'virt-make-fs' to create
a msdos/vfat filesystem you're fairly well bound to hit the
following annoying error:

virt-make-fs: error copying contents into filesystem
An error here usually means that the program did not estimate the
filesystem size correctly.  Please read the BUGS section of the manpage.
tar_in: tar subcommand failed on directory: /: tar: ./answerfile: Cannot change ownership to uid 500, gid 500: Operation not permitted
tar: .: Cannot change ownership to uid 500, gid 500: Operation not permitted

Although it is well understood why this error occurs, we really
should just make it work.

It seems as if passing tar --no-same-owner would fix this.  We
could change the tar-in APIs to allow this and other flags.

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

libguestfs 1.19.19
Comment 1 Richard W.M. Jones 2012-07-18 12:10:26 UTC 
Fixed upstream in these commits:
781857a86b3bc8238995a9212ea09aa368fc2fc9
50780a84f65ec5d76605691cea889392c2730f54
and in libguestfs >= 1.19.21.