From: Dave Chinner <david@fromorbit.com>
To: Tom Crane <T.Crane@rhul.ac.uk>
Cc: xfs@oss.sgi.com
Subject: Re: xfs_fsr (defragmenting) 'XFS_IOC_SWAPEXT failed: ino=xxxxxx: Invalid argument' error
Date: Wed, 15 Feb 2012 11:28:11 +1100 [thread overview]
Message-ID: <20120215002811.GM7479@dastard> (raw)
In-Reply-To: <4F3AAC04.5090400@rhul.ac.uk>
On Tue, Feb 14, 2012 at 06:46:28PM +0000, Tom Crane wrote:
> Dear XFS Support,
> I am attempting to use xfs_fsr to defrag a 60TB FS but am getting
> some of the following errors;
> 'XFS_IOC_SWAPEXT failed: ino=xxxxxx: Invalid argument'. Most files
> defrag w/o problem. In an hour long run only 45/(45+6211) failed
> this way. Here is a example chunk of syslog from a run with fsr -v
> which includes the FS level reports.
.....
> >Feb 14 15:49:15 store3 fsr[10917]: ino=797728
> >Feb 14 15:49:17 store3 kernel: Filesystem dm-0:
> >fs/xfs/xfs_dfrag.c: inode 0xc2c20 format is incompatible for exchanging.
> >Feb 14 15:49:17 store3 fsr[10917]: XFS_IOC_SWAPEXT failed: ino=797728: Invalid argument
Which means the kernel caught a condition where the extent swap
could not be done due to differences in the layout of the two
inodes. If we do the swap we corrupt the filesystem, so we abort
and return an error instead.
http://permalink.gmane.org/gmane.comp.file-systems.xfs.general/40013
http://www.spinics.net/lists/xfs/msg09736.html
> Is this a known problem with xfs in this kernel? Any other
> information/tests that I can supply?
No problems with the kernel. Deficiencies are on the userspace side
with how xfs_fsr is setting up the attribute fork on the donor
inode. The event tracing indicated in the second link above will
tell us what the incomaptibility is and maybe how to improve xfs_fsr
t0 avoid it...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-02-15 0:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-14 18:46 xfs_fsr (defragmenting) 'XFS_IOC_SWAPEXT failed: ino=xxxxxx: Invalid argument' error Tom Crane
2012-02-14 23:24 ` Eric Sandeen
2012-02-21 13:00 ` Tom Crane
2012-02-15 0:28 ` Dave Chinner [this message]
2012-02-15 1:32 ` Dave Chinner
2012-02-15 13:15 ` Michael Monnerie
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=20120215002811.GM7479@dastard \
--to=david@fromorbit.com \
--cc=T.Crane@rhul.ac.uk \
--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