xfs
[Top] [All Lists]

Re: rfc: kill ino64 mount option

To: markgw@xxxxxxx
Subject: Re: rfc: kill ino64 mount option
From: Christoph Litauer <litauer@xxxxxxxxxxxxxx>
Date: Tue, 01 Jul 2008 16:45:07 +0200
Cc: Christoph Hellwig <hch@xxxxxx>, xfs@xxxxxxxxxxx
In-reply-to: <486A3B5B.20402@xxxxxxx>
References: <20080627153928.GA31384@xxxxxx> <20080628000914.GE29319@disturbed> <486589E7.9010705@xxxxxxx> <4869E5A4.4020900@xxxxxxxxxxxxxx> <486A3B5B.20402@xxxxxxx>
Sender: xfs-bounce@xxxxxxxxxxx
User-agent: Thunderbird 2.0.0.14 (Macintosh/20080421)
Mark Goodwin schrieb:


Christoph Litauer wrote:
Mark Goodwin schrieb:
..
We have a design proposal known as "inode32+" that essentially removes
the direct mapping between inode number and disk offset. This will
provide all the layout and performance benefits of ino64 without the
interop issues.  Until inode32+ is available, we need to keep ino64.

Hi,

as I have massive performance problems using xfs with millions of
inodes, I am very interested in this "incode32+".

can you please post some details of the problems you're seeing?

Please see thread "Performance problems with millions of inodes". If you don't have it anymore, I can send it to you.


My server is a 32 bit machine, so I am not able to use inode64.
Is it available?

inode32+ is only a design at the moment. An implementation is several
months away. Until then, you'll have to update your server to 64bit.

This is, sadly, not an option at the moment ...

--
Regards
Christoph
________________________________________________________________________
Christoph Litauer                  litauer@xxxxxxxxxxxxxx
Uni Koblenz, Computing Center,     http://www.uni-koblenz.de/~litauer
Postfach 201602, 56016 Koblenz     Fon: +49 261 287-1311, Fax: -100 1311
PGP-Fingerprint: F39C E314 2650 650D 8092 9514 3A56 FBD8 79E3 27B2


<Prev in Thread] Current Thread [Next in Thread>