Hello,
the wiki page about Lustre debugging has a bug itself ;)
<quote>
Debug daemon commands
[...]
file size limit. To decode the dumped file to ASCII and order the log entries
by time, run:
sort -k4 -t: > {newfile}
</quote>
Well, running this command certainly won''t decode anything. I guess the
correct command would be:
lctl debug_file $path_to_debugfile | sort -k4 -t:
Cheers,
Bernd
--
Bernd Schubert
Q-Leap Networks GmbH
On Jul 25, 2008 17:55 +0200, Bernd Schubert wrote:> the wiki page about Lustre debugging has a bug itself ;) > > <quote> > Debug daemon commands > > [...] > > file size limit. To decode the dumped file to ASCII and order the log entries > by time, run: > sort -k4 -t: > {newfile} > </quote> > > Well, running this command certainly won''t decode anything. I guess the > correct command would be: > > lctl debug_file $path_to_debugfile | sort -k4 -t:To be honest, there is no need for the "sort" anymore, as this is done internally by lctl using quicksort. The documentation should just remove that. Cheers, Andreas -- Andreas Dilger Sr. Staff Engineer, Lustre Group Sun Microsystems of Canada, Inc.
On Sat, Jul 26, 2008 at 03:54:12PM -0400, Andreas Dilger wrote:> On Jul 25, 2008 17:55 +0200, Bernd Schubert wrote: > > the wiki page about Lustre debugging has a bug itself ;) > > > > <quote> > > Debug daemon commands > > > > [...] > > > > file size limit. To decode the dumped file to ASCII and order the log entries > > by time, run: > > sort -k4 -t: > {newfile} > > </quote> > > > > Well, running this command certainly won''t decode anything. I guess the > > correct command would be: > > > > lctl debug_file $path_to_debugfile | sort -k4 -t: > > To be honest, there is no need for the "sort" anymore, as this is done > internally by lctl using quicksort. The documentation should just > remove that.This explains why I never saw much difference. I just corrected the wiki page, actually the correct command was already there, only the wiki syntax was wrong. Cheers, Bernd