X-Git-Url: https://git.whamcloud.com/?a=blobdiff_plain;f=LustreDebugging.xml;h=fcd030db0c705a7a5dc220e49528386a60a495af;hb=747cfe232f70780cd5f35174340075d19e2cf8f1;hp=eb5b1a2f3cc35ef95bcdc327a125e5db2444b130;hpb=6f3a9ccbfe770228a927c37b9e2607525799dbb9;p=doc%2Fmanual.git
diff --git a/LustreDebugging.xml b/LustreDebugging.xml
index eb5b1a2..fcd030d 100644
--- a/LustreDebugging.xml
+++ b/LustreDebugging.xml
@@ -646,24 +646,29 @@ Debug log: 324 lines, 258 kept, 66 dropped.
attributes for a new file or directory.
The lfs getstripe command takes a Lustre filename as input and lists
all the objects that form a part of this file. To obtain this information for the file
- /mnt/lustre/frog in a Lustre file system, run:
- $ lfs getstripe /mnt/lustre/frog
+ /mnt/testfs/frog in a Lustre file system, run:
+ $ lfs getstripe /mnt/testfs/frog
lmm_stripe_count: 2
lmm_stripe_size: 1048576
+lmm_pattern: 1
+lmm_layout_gen: 0
lmm_stripe_offset: 2
obdidx objid objid group
2 818855 0xc7ea7 0
0 873123 0xd52a3 0
- The debugfs tool is provided in the e2fsprogs
- package. It can be used for interactive debugging of an ldiskfs file
- system. The debugfs tool can either be used to check status or modify
- information in the file system. In a Lustre file system, all objects that belong to a file
- are stored in an underlying ldiskfs file system on the OSTs. The file
- system uses the object IDs as the file names. Once the object IDs are known, use the
- debugfs tool to obtain the attributes of all objects from different
- OSTs.
- A sample run for the /mnt/lustre/frog file used in the above example is shown here:
+ The debugfs tool is provided in the
+ e2fsprogs package. It can be used for interactive
+ debugging of an ldiskfs file system. The
+ debugfs tool can either be used to check status or
+ modify information in the file system. In a Lustre file system, all
+ objects that belong to a file are stored in an underlying
+ ldiskfs file system on the OSTs. The file system
+ uses the object IDs as the file names. Once the object IDs are known,
+ use the debugfs tool to obtain the attributes of
+ all objects from different OSTs.
+ A sample run for the /mnt/testfs/frog file used
+ in the above example is shown here:
$ debugfs -c -R "stat O/0/d$((818855 % 32))/818855" /dev/vgmyth/lvmythost2
debugfs 1.41.90.wc3 (28-May-2011)
@@ -717,6 +722,13 @@ Filesystem volume name: myth-OST0004
lctl> show dlmtrace
lctl> debug_kernel [filename]
+
+ Controlling Console Message Rate Limiting
+ Some console messages which are printed by Lustre are rate limited. When such messages are printed, they may be followed by a message saying "Skipped N previous similar message(s)," where N is the number of messages skipped. This rate limiting can be completely disabled by a libcfs module parameter called libcfs_console_ratelimit. To disable console message rate limiting, add this line to /etc/modprobe.d/lustre.conf and then reload Lustre modules.
+ options libcfs libcfs_console_ratelimit=0
+ It is also possible to set the minimum and maximum delays between rate-limited console messages using the module parameters libcfs_console_max_delay and libcfs_console_min_delay. Set these in /etc/modprobe.d/lustre.conf and then reload Lustre modules. Additional information on libcfs module parameters is available via modinfo:
+ modinfo libcfs
+
debuggingdevelopers toolsLustre Debugging for Developers