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 12:32:17 +1100 [thread overview]
Message-ID: <20120215013217.GK14132@dastard> (raw)
In-Reply-To: <20120215002811.GM7479@dastard>
On Wed, Feb 15, 2012 at 11:28:11AM +1100, Dave Chinner wrote:
> http://www.spinics.net/lists/xfs/msg09736.html
Well, that shows how slow the XFS mailing list can be at times. I
found Eric's reply in this thread in an internet archive via google
before it arrived in my inbox. IOWs, the the mail archive site
received it, published it and google crawled it before the XFS list
finished distributing the mail to all recipiants....
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 1:32 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
2012-02-15 1:32 ` Dave Chinner [this message]
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=20120215013217.GK14132@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