From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <xfs-bounces@oss.sgi.com>
Received: from cuda.sgi.com (cuda2.sgi.com [192.48.176.25])
	by oss.sgi.com (8.14.3/8.14.3/SuSE Linux 0.8) with ESMTP id
	q1FDFs8p179533 for <xfs@oss.sgi.com>; Wed, 15 Feb 2012 07:15:54 -0600
Received: from mailsrv14.zmi.at (mailsrv14.zmi.at [212.69.164.54]) by
	cuda.sgi.com with ESMTP id KuStg2npE70tkqaJ (version=TLSv1
	cipher=AES256-SHA bits=256 verify=NO) for <xfs@oss.sgi.com>;
	Wed, 15 Feb 2012 05:15:50 -0800 (PST)
From: Michael Monnerie <michael.monnerie@is.it-management.at>
Subject: Re: xfs_fsr (defragmenting) 'XFS_IOC_SWAPEXT failed: ino=xxxxxx:
	Invalid argument' error
Date: Wed, 15 Feb 2012 14:15:48 +0100
Message-ID: <2163035.tNpyZ9uoXp@saturn>
In-Reply-To: <20120215013217.GK14132@dastard>
References: <4F3AAC04.5090400@rhul.ac.uk> <20120215002811.GM7479@dastard>
	<20120215013217.GK14132@dastard>
MIME-Version: 1.0
List-Id: XFS Filesystem from SGI <xfs.oss.sgi.com>
List-Unsubscribe: <http://oss.sgi.com/mailman/options/xfs>,
	<mailto:xfs-request@oss.sgi.com?subject=unsubscribe>
List-Archive: <http://oss.sgi.com/pipermail/xfs>
List-Post: <mailto:xfs@oss.sgi.com>
List-Help: <mailto:xfs-request@oss.sgi.com?subject=help>
List-Subscribe: <http://oss.sgi.com/mailman/listinfo/xfs>,
	<mailto:xfs-request@oss.sgi.com?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0414889795396811279=="
Sender: xfs-bounces@oss.sgi.com
Errors-To: xfs-bounces@oss.sgi.com
To: xfs@oss.sgi.com
Cc: Tom Crane <T.Crane@rhul.ac.uk>


--===============0414889795396811279==
Content-Type: multipart/signed; boundary="nextPart2464982.iUZAsmCBqb"; micalg="pgp-sha1"; protocol="application/pgp-signature"
Content-Transfer-Encoding: quoted-printable


--nextPart2464982.iUZAsmCBqb
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"

Am Mittwoch, 15. Februar 2012, 12:32:17 schrieb Dave Chinner:
> 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....

Maybe they are not using XFS as their mail spool dir filesystem? ;-)

--=20
mit freundlichen Gr=C3=BCssen,
Michael Monnerie, Ing. BSc

it-management Internet Services: Prot=C3=A9ger
http://proteger.at [gesprochen: Prot-e-schee]
Tel: +43 660 / 415 6531

--nextPart2464982.iUZAsmCBqb
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)

iEYEABECAAYFAk87sAQACgkQzhSR9xwSCbThMACgueMMPV1LX0RKBAmjsDWRqAXh
ycwAoLIa+6yCf8vEpT97gVUB9UP+si5s
=zOzT
-----END PGP SIGNATURE-----

--nextPart2464982.iUZAsmCBqb--


--===============0414889795396811279==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

--===============0414889795396811279==--