[Lustre-discuss] Making a init script

[Andreas Dilger]

On Jul 12, 2008  14:07 +0900, Satoshi Isono wrote:
> Thanks for useful information.
> Is what is necessary to execute this command on a client only at once? 
> And this is performed by all clients, right?

This command should be run once on the MGS node (usually the same as the
MDS node).  It will take effect for already mounted clients very soon, and
for all new mounts at mount time.

> Also, I want to get more information about this function atatahead. From 
> what can I get information?
>
> I realize this problem is bug (Bugzilla: #15406 #15169 #15175). Better 
> solution is to upgrade Lustre 1.6.5.1, how do you think so?

Yes, that is another possibility.

> At 08/07/12（土）06:19, Andreas Dilger wrote:
>> On Jul 11, 2008  11:27 +0900, Satoshi Isono wrote:
>> > I am using lustre-1.6.4.3 on RHEL 5.1 with kernel 2.6.18. And then, I
>> > found Lustre bug statahead function on this Lustre version. I try to
>> > write the following entry into the Lustre init script in order to set
>> > this value permently. In which file should I write?
>> >
>> > echo 0 > /proc/fs/lustre/llite/*/statahead_max
>> >
>> > I have already tested. In case of editting /etc/rc.d/ec.local, it did
>> > not work. I assume I have to do this operation before mounting
>> > Lustre, after loading Lustre modules.
>>
>> The rc.local script is likely run BEFORE Lustre is mounted.  The above
>> parameter needs to be set AFTER Lustre is mounted.  You can add a
>> permanent configuration parameter with:
>>
>>         lctl conf_param lustre.llite.statahead_max=0
>>
>> Note that this is permanent and you will need to reset this parameter
>> later with a new setting to re-enable the statahead:
>>
>>         lctl conf_param lustre.llite.statahead_max=32
>>
>> Cheers, Andreas
>> --
>> Andreas Dilger
>> Sr. Staff Engineer, Lustre Group
>> Sun Microsystems of Canada, Inc.

Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.