From: Christoph Hellwig <hch@infradead.org>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: migration to selinux + xfs_fsr oddity....
Date: Tue, 12 May 2009 12:04:03 -0400 [thread overview]
Message-ID: <20090512160403.GB28714@infradead.org> (raw)
In-Reply-To: <49FF9B8E.7040607@sandeen.net>
On Mon, May 04, 2009 at 08:51:10PM -0500, Eric Sandeen wrote:
> This came up in RH Bugzilla #498860, "xfs_fsr fails to complete"
>
> The reporter had an existing xfs filesystem from another Linux OS, and
> was using it under Fedora now. He had some files for which xfs_fsr
> bails out with EINVAL:
>
> XFS_IOC_SWAPEXT failed: fragfile: Invalid argument
As analyzed in the bugzilla this is a problem when selinux attributes
are created underneath due to selinux.
Either we relax the attribute fork check an allow the new inode to have
an attribute fork despite the old one not having one, or we need to
create a fake xattr on the file to be defragmented.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2009-05-12 16:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-05 1:51 migration to selinux + xfs_fsr oddity Eric Sandeen
2009-05-12 16:04 ` Christoph Hellwig [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090512160403.GB28714@infradead.org \
--to=hch@infradead.org \
--cc=sandeen@sandeen.net \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox