Hi, Lustre manual 1.6 v18 says that that in production lustre debug level should be set to fairly low. Manual also says that I can verify that level by running following commands: # sysctl portals.debug This gives ne following error error: ''portals.debug'' is an unknown key cat /proc/sys/lnet/debug gives output: ioctl neterror warning error emerg ha config console cat /proc/sys/lnet/subsystem_debug undefined mdc mds osc ost class log llite rpc lnet lnd pinger filter echo ldlm lov lmv sec gss mgc mgs fid fld manual says that in order to set reasonable production debug level one need to put numeric value into debug files like below: echo 0x3f0400 > /proc/sys/lnet/debug Will this work under lustre 1.6.3 or maybe it is old reference from 1.4 release and there is new way of changing lustre debug level in new releases? Thanks, Wojciech Turek -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.lustre.org/pipermail/lustre-discuss/attachments/20071116/3944e4bc/attachment-0002.html
Hi,
There is one way i use here, using sysctl to set lnet.debug = 0
Regards
Balagopal
Wojciech Turek wrote:> Hi,
>
> Lustre manual 1.6 v18 says that that in production lustre debug level
> should be set to fairly low. Manual also says that I can verify that
> level by running following commands:
> # sysctl portals.debug
> This gives ne following error
> error: ''portals.debug'' is an unknown key
>
> cat /proc/sys/lnet/debug
> gives output:
> ioctl neterror warning error emerg ha config console
>
> cat /proc/sys/lnet/subsystem_debug
> undefined mdc mds osc ost class log llite rpc lnet lnd pinger filter
> echo ldlm lov lmv sec gss mgc mgs fid fld
>
> manual says that in order to set reasonable production debug level one
> need to put numeric value into debug files like below:
> echo 0x3f0400 > /proc/sys/lnet/debug
> Will this work under lustre 1.6.3 or maybe it is old reference from
> 1.4 release and there is new way of changing lustre debug level in new
> releases?
>
> Thanks,
>
> Wojciech Turek
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Lustre-discuss mailing list
> Lustre-discuss at clusterfs.com
> https://mail.clusterfs.com/mailman/listinfo/lustre-discuss
>
Wojciech Turek wrote:> Hi, > > Lustre manual 1.6 v18 says that that in production lustre debug level > should be set to fairly low. Manual also says that I can verify that > level by running following commands: > # sysctl portals.debug > This gives ne following error > error: ''portals.debug'' is an unknown keySigh. This is another error in the manual. As you might suspect, the correct answer is ''lnet.debug'' # sysctl lnet.debug lnet.debug = ioctl neterror warning error emerg ha config console> > cat /proc/sys/lnet/debug > gives output: > ioctl neterror warning error emerg ha config console > > cat /proc/sys/lnet/subsystem_debug > undefined mdc mds osc ost class log llite rpc lnet lnd pinger filter > echo ldlm lov lmv sec gss mgc mgs fid fld > > manual says that in order to set reasonable production debug level one > need to put numeric value into debug files like below: > echo 0x3f0400 > /proc/sys/lnet/debug > Will this work under lustre 1.6.3 or maybe it is old reference from 1.4 > release and there is new way of changing lustre debug level in new > releases?The hex bitmasks will work with 1.6.3, however we have added nice human-readable strings. ''-1'' will still set all values ''on'' and is a simple way to see the entire list.. # echo -1 > /proc/sys/lnet/debug # cat /proc/sys/lnet/debug trace inode super ext2 malloc cache info ioctl neterror net warning buffs other dentry nettrace page dlmtrace error emerg ha rpctrace vfstrace reada mmap config console quota sec # echo "ioctl neterror warning error emerg ha config console" > /proc/sys/lnet/debug # cat /proc/sys/lnet/debug ioctl neterror warning error emerg ha config console cliffw> > Thanks, > > Wojciech Turek > > > > ------------------------------------------------------------------------ > > _______________________________________________ > Lustre-discuss mailing list > Lustre-discuss at clusterfs.com > https://mail.clusterfs.com/mailman/listinfo/lustre-discuss
Hi Cliff, Thanks for exhaustive answer. Is that mean that in lustre 1.6.3 by default debug level is set for production lustre? Do you have any suggestions what I could "turn off" to get better performance? Cheers, Wojciech On 16 Nov 2007, at 17:10, Cliff White wrote:> Wojciech Turek wrote: >> Hi, >> Lustre manual 1.6 v18 says that that in production lustre debug >> level should be set to fairly low. Manual also says that I can >> verify that level by running following commands: >> # sysctl portals.debug >> This gives ne following error >> error: ''portals.debug'' is an unknown key > > Sigh. This is another error in the manual. As you might suspect, > the correct answer is ''lnet.debug'' > > # sysctl lnet.debug > lnet.debug = ioctl neterror warning error emerg ha config console > >> cat /proc/sys/lnet/debug >> gives output: >> ioctl neterror warning error emerg ha config console >> cat /proc/sys/lnet/subsystem_debug >> undefined mdc mds osc ost class log llite rpc lnet lnd pinger >> filter echo ldlm lov lmv sec gss mgc mgs fid fld >> manual says that in order to set reasonable production debug level >> one need to put numeric value into debug files like below: >> echo 0x3f0400 > /proc/sys/lnet/debug >> Will this work under lustre 1.6.3 or maybe it is old reference >> from 1.4 release and there is new way of changing lustre debug >> level in new releases? > > The hex bitmasks will work with 1.6.3, however we have added nice > human-readable strings. ''-1'' will > still set all values ''on'' and is a simple way to see the entire list.. > > > # echo -1 > /proc/sys/lnet/debug > > # cat /proc/sys/lnet/debug > trace inode super ext2 malloc cache info ioctl neterror net warning > buffs other dentry nettrace page dlmtrace error emerg ha rpctrace > vfstrace reada mmap config console quota sec > > # echo "ioctl neterror warning error emerg ha config console" > / > proc/sys/lnet/debug > # cat /proc/sys/lnet/debug > ioctl neterror warning error emerg ha config console > > cliffw > > > > >> Thanks, >> Wojciech Turek >> --------------------------------------------------------------------- >> --- >> _______________________________________________ >> Lustre-discuss mailing list >> Lustre-discuss at clusterfs.com >> https://mail.clusterfs.com/mailman/listinfo/lustre-discuss >Mr Wojciech Turek Assistant System Manager University of Cambridge High Performance Computing service email: wjt27 at cam.ac.uk tel. +441223763517 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.lustre.org/pipermail/lustre-discuss/attachments/20071116/e74ad227/attachment-0002.html
Wojciech Turek wrote:> Hi Cliff, > > Thanks for exhaustive answer. > Is that mean that in lustre 1.6.3 by default debug level is set for > production lustre? > Do you have any suggestions what I could "turn off" to get better > performance? >I have not tested this with 1.6, but on 1.4 all debug has some performance impact, so we suggest ''0'' (all off) for best performance. cliffw
On Fri, Nov 16, 2007 at 09:10:49AM -0800, Cliff White wrote: [......]> The hex bitmasks will work with 1.6.3, however we have added nice > human-readable strings. ''-1'' will > still set all values ''on'' and is a simple way to see the entire list.. > > > # echo -1 > /proc/sys/lnet/debug > > # cat /proc/sys/lnet/debug > trace inode super ext2 malloc cache info ioctl neterror net warning > buffs other dentry nettrace page dlmtrace error emerg ha rpctrace > vfstrace reada mmap config console quota sec > > # echo "ioctl neterror warning error emerg ha config console" > > /proc/sys/lnet/debug > # cat /proc/sys/lnet/debug > ioctl neterror warning error emerg ha config console >It''s also easy to turn on/off individual values without changing the rest: # echo + neterror > /proc/sys/lnet/debug # echo - neterror > /proc/sys/lnet/debug HTH, Isaac