Re: inode64 workaround

[David Chatterton <chatz@melbourne.sgi.com>]

This is a sysctl, see sysctl(8).

It was introduced to XFS in October 2004, I'm not sure if it made 2.6.9.

If this doesn't help a little then I'm unsure why you think that inode64 is
going to solve your problem?

David


Deanan wrote:
> Hi David,
> 
> I'm not sure if it will help but I'd like to try.
> Where do you set the rotor?
>  BTW< tis particular box is 2.6.9.
> 
> Thanks,
> 
> Deanan
> 
> 
>> Deanan,
>>
>> Would something like the inode rotor help?
>>
>>   fs.xfs.rotorstep              (Min: 1  Default: 1  Max: 256)
>>
>>         In "inode32" allocation mode, this option determines how many
>>
>>         files the allocator attempts to allocate in the same allocation
>>
>>         group before moving to the next allocation group.  The intent
>>
>>         is to control the rate at which the allocator moves between
>>
>>         allocation groups when allocating extents for new files.
>>
>> David
>>
>>
>> Deanan wrote:
>>   
>>> Hi,
>>>
>>> I've got some systems that I can't change the kernel on (external
>>> vendor) that
>>> are 32bit but I'm running into the performance problem that is fixed by
>>> using
>>> inode64. Is there any known way of working around the problem on a 32bit
>>> kernel?
>>>
>>> In our case, the problem occurs as soon as you start to delete files and
>>> write new ones.
>>>
>>> Cheers,
>>>
>>> Deanan
>>>
>>>     
>>
>>   
> 

-- 
David Chatterton
XFS Engineering Manager
SGI Australia