[LU-6268] lctl in interactive mode fails to parse get_param requests when run after get_param -n

Duplicate — Thu, 26 Feb 2015 15:04:40 +0000

When running lctl interactively, it fails to parse commands when run in a certain order. For example:

12:46:09 (pts/1:skein1.ccs.ornl.gov)% lctl |~/src/melt
lctl > get_param -n osc.*.stats
snapshot_time 1424454461.933397 secs.usecs
req_waittime 234972 samples [usec] 108 5063035 306162221 75801966615113
req_active 234972 samples [reqs] 1 7 241025 255209
read_bytes 33525 samples [bytes] 294912 1048576 35150017444 36855368470308624
write_bytes 59583 samples [bytes] 116 1048576 62473570980 65506751073897104
ost_setattr 20 samples [usec] 362 22779 33394 525105442
ost_read 33525 samples [usec] 1318 108696 110832848 493077777590
ost_write 59583 samples [usec] 1288 5063035 126267741 74861672349603
<snip>
ost_connect 1 samples [usec] 872 872 872 760384
ost_punch 3 samples [usec] 24060 58101 126686 5937085426
ost_statfs 16934 samples [usec] 138 11406 5861480 2518858106
ldlm_cancel 153 samples [usec] 139 10846 79772 207940048
obd_ping 120839 samples [usec] 109 10620 26991886 6713103412
lctl > get_param osc.knotfs-OST0037-osc-ffff8807eab68c00.cur_dirty_bytes
get_param: invalid option – '('
get the Lustre or LNET parameter
usage: get_param [-n|-N|-F] <param_path1 param_path2 ...>
Get the value of Lustre or LNET parameter from the specified path.
The path can contain shell-style filename patterns.
-n Print only the value and not parameter name.
-N Print only matched parameter names and not the values.
(Especially useful when using patterns.)
-F When -N specified, add '/', '@' or '=' for directories,
symlinks and writeable files, respectively.

Whamcloud Community JIRA

[LU-6268] lctl in interactive mode fails to parse get_param requests when run after get_param -n