From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs@oss.sgi.com
Cc: Tom Crane <T.Crane@rhul.ac.uk>
Subject: Re: xfs_fsr (defragmenting) 'XFS_IOC_SWAPEXT failed: ino=xxxxxx: Invalid argument' error
Date: Wed, 15 Feb 2012 14:15:48 +0100 [thread overview]
Message-ID: <2163035.tNpyZ9uoXp@saturn> (raw)
In-Reply-To: <20120215013217.GK14132@dastard>
[-- Attachment #1.1: Type: text/plain, Size: 649 bytes --]
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? ;-)
--
mit freundlichen Grüssen,
Michael Monnerie, Ing. BSc
it-management Internet Services: Protéger
http://proteger.at [gesprochen: Prot-e-schee]
Tel: +43 660 / 415 6531
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2012-02-15 13:15 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
2012-02-15 13:15 ` Michael Monnerie [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=2163035.tNpyZ9uoXp@saturn \
--to=michael.monnerie@is.it-management.at \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.