From: Richard Ems <richard.ems@cape-horn-eng.com>
To: xfs@oss.sgi.com
Subject: Re: XFS unlink still slow on 3.1.9 kernel ?
Date: Wed, 15 Feb 2012 13:48:56 +0100 [thread overview]
Message-ID: <4F3BA9B8.4080204@cape-horn-eng.com> (raw)
In-Reply-To: <20120214190753.GA8383@infradead.org>
On 02/14/2012 08:07 PM, Christoph Hellwig wrote:
> On Tue, Feb 14, 2012 at 07:12:29PM +0100, Richard Ems wrote:
>> # /net/c3m/usr/local/software/XFS/summarise_stat.pl /bin/
>> 9 6.2% are scripts (shell, perl, whatever)
>> 65 44.8% don't use any stat() family calls at all
>> 61 42.1% use 32-bit stat() family interfaces only
>> 9 6.2% use 64-bit stat64() family interfaces only
>> 1 0.7% use both 32-bit and 64-bit stat() family interfaces
>>
>> So I was not sure if I should use inode64 or not.
>
> Are you on a 32-bit system (userspace, kernel doesn't matter)?
No, I have been running on 64-bit systems for years. That output above
is on openSUSE 12.1 64-bit.
> If the system is 64-bit even the plain stat handles 64-bit inodes just
> fine.
With *plain stat* you mean the *32-bit stat* listed above ?
Is it then safe to switch all XFS partitions to be mounted with inode64
on 64-bit systems? Also for NFS v3 exports?
>From the XFS FAQ I read that it should work, also for NFS v3, and that I
can try it and switch back if there are problems, so I will give it a try!
Many thanks again for your time and help!
Richard
--
Richard Ems mail: Richard.Ems@Cape-Horn-Eng.com
Cape Horn Engineering S.L.
C/ Dr. J.J. Dómine 1, 5º piso
46011 Valencia
Tel : +34 96 3242923 / Fax 924
http://www.cape-horn-eng.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-02-15 12:48 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-14 13:02 XFS unlink still slow on 3.1.9 kernel ? Richard Ems
[not found] ` <4F3AA191.9030606@mnsu.edu>
2012-02-14 18:12 ` Richard Ems
2012-02-14 19:07 ` Christoph Hellwig
2012-02-15 12:48 ` Richard Ems [this message]
2012-02-14 23:10 ` Stan Hoeppner
2012-02-15 15:54 ` Richard Ems
-- strict thread matches above, loose matches on Subject: below --
2012-02-13 16:57 Richard Ems
2012-02-13 17:08 ` Christoph Hellwig
2012-02-13 17:11 ` Richard Ems
2012-02-13 17:15 ` Christoph Hellwig
2012-02-13 17:26 ` Richard Ems
2012-02-13 17:29 ` Christoph Hellwig
2012-02-13 17:53 ` Richard Ems
2012-02-13 18:02 ` Christoph Hellwig
2012-02-13 18:06 ` Richard Ems
2012-02-13 18:10 ` Christoph Hellwig
2012-02-13 18:18 ` Richard Ems
2012-02-13 18:48 ` Richard Ems
2012-02-13 21:16 ` Christoph Hellwig
2012-02-14 5:31 ` Stan Hoeppner
2012-02-14 9:48 ` Richard Ems
2012-02-14 19:43 ` Christoph Hellwig
2012-02-14 9:49 ` Richard Ems
2012-02-14 10:54 ` Richard Ems
2012-02-14 11:44 ` Richard Ems
2012-02-14 0:09 ` Dave Chinner
2012-02-14 12:32 ` Richard Ems
2012-02-14 19:45 ` Christoph Hellwig
2012-02-15 12:07 ` Richard Ems
2012-02-15 1:27 ` Dave Chinner
2012-02-15 12:07 ` Richard Ems
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=4F3BA9B8.4080204@cape-horn-eng.com \
--to=richard.ems@cape-horn-eng.com \
--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