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?
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.
Thanks
-- Mark
|