From: Dave Chinner <david@fromorbit.com>
To: "Linda A. Walsh" <xfs@tlinx.org>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: xfs: xfs_swap_extents needs to handle dynamic fork offsets
Date: Tue, 9 Aug 2011 10:04:17 +1000 [thread overview]
Message-ID: <20110809000417.GO3162@dastard> (raw)
In-Reply-To: <4E406ECD.2020708@tlinx.org>
On Mon, Aug 08, 2011 at 04:18:37PM -0700, Linda A. Walsh wrote:
> I'm seeing several of these in 'dmesg':
>
> [873569.328221] Filesystem dm-6: fs/xfs/xfs_dfrag.c: inode
> 0x8227a310 format is incompatible for exchanging.
> [873623.752724] Filesystem dm-6: fs/xfs/xfs_dfrag.c: inode
> 0x8227a310 format is incompatible for exchanging.
> [873669.721127] Filesystem dm-6: fs/xfs/xfs_dfrag.c: inode
> 0x8227a310 format is incompatible for exchanging.
> ...
>
> ----
> am running 2.6.38.3,
>
> & version 3.1.4-2.1 of 'xfsprogs'....
That's no surprise - there are still some formats of inodes that we
cannot exchange because the code in xfs_fsr cannot precisely control
the format of the inode forks from userspace. If you use the event
tracing to capture the before and after swap extent trace points, I
can tell you why they were incompatible for exchange, and whether
xfs_fsr can be further modified to enable those files to be
defragmented....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2011-08-09 0:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-08 23:18 xfs: xfs_swap_extents needs to handle dynamic fork offsets Linda A. Walsh
2011-08-09 0:04 ` Dave Chinner [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=20110809000417.GO3162@dastard \
--to=david@fromorbit.com \
--cc=xfs@oss.sgi.com \
--cc=xfs@tlinx.org \
/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