Lustre discuss - Apr 2009 - lustre 1.6.7.1 checksum_type setting verification

We have compiled lustre with --disable checksum as a performance  
enhancement on 1.6.7.1  and would like to verify that this is actually  
in affect.  Reviewing /proc/fs/lustre/osc/*/checksum_type we see two  
responses across all of the test system nodes

mtg[1-2],mtn1sm,mtt[1-2]
----------------
  crc32 [adler]
  crc32 [adler]
  crc32 [adler]
  crc32 [adler]
  crc32 [adler]
  crc32 [adler]
----------------
mtmds1
----------------
  [crc32]
  [crc32]
  [crc32]
  [crc32]
  [crc32]
  [crc32]

Is this an indication that the checksum is running?    Is there a way  
to verify directly that checksum is disabled or not?

On Apr 30, 2009, at 8:43 PM, jan julian wrote:
> We have compiled lustre with --disable checksum as a performance
> enhancement on 1.6.7.1  and would like to verify that this is actually
> in affect.  Reviewing /proc/fs/lustre/osc/*/checksum_type
You should check /proc/fs/lustre/osc/*/chechsums instead of  
checksum_type
(lctl get_param osc.*.checksums). If it is set to 0, it means that  
check-summing
is disabled.

Johann

Thanks Johann

They show up in /proc/fs/lustre/osc/*/checksums as off.

Jan

On Apr 30, 2009, at 11:51 AM, Johann Lombardi wrote:
> On Apr 30, 2009, at 8:43 PM, jan julian wrote:
>> We have compiled lustre with --disable checksum as a performance
>> enhancement on 1.6.7.1  and would like to verify that this is  
>> actually
>> in affect.  Reviewing /proc/fs/lustre/osc/*/checksum_type
>
> You should check /proc/fs/lustre/osc/*/chechsums instead of  
> checksum_type
> (lctl get_param osc.*.checksums). If it is set to 0, it means that  
> check-summing
> is disabled.
>
> Johann