Details
-
Bug
-
Resolution: Fixed
-
Major
-
None
-
None
-
3
-
9223372036854775807
Description
The following huge output of test_133g is not correct. It means "find" does not include its "-name $PARAM" argument.
== sanity test 133g: Check reads/writes of server lustre proc files with bad area io ========================================================== 16:13:38 (1683821618) CMD: onyx-103vm7 /usr/sbin/lctl get_param -n version 2>/dev/null CMD: onyx-103vm7 /usr/sbin/lctl list_param -FR '*' | grep '=' | tr -d = | egrep -v 'force_lbug|changelog_mask|daemon_file' | xargs -n 1 find /proc/fs/lustre/ /sys/fs/lustre/ /sys/kernel/debug/lnet/ /sys/kernel/debug/lustre/ -name | xargs -n 1 badarea_io onyx-103vm7: find: 'at_early_margin': No such file or directory onyx-103vm7: find: 'at_extra': No such file or directory /proc/fs/lustre/ /proc/fs/lustre/lmv /proc/fs/lustre/lod /proc/fs/lustre/lod/lustre-MDT0000-mdtlov /proc/fs/lustre/lod/lustre-MDT0000-mdtlov/pool /proc/fs/lustre/lod/lustre-MDT0000-mdtlov/pools /proc/fs/lustre/lod/lustre-MDT0000-mdtlov/mdt_obd /proc/fs/lustre/lod/lustre-MDT0000-mdtlov/target_obd /proc/fs/lustre/lov /proc/fs/lustre/lov/lustre-MDT0000-mdtlov /proc/fs/lustre/mdc /proc/fs/lustre/mdt /proc/fs/lustre/mdt/lustre-MDT0000 /proc/fs/lustre/mdt/lustre-MDT0000/exports /proc/fs/lustre/mdt/lustre-MDT0000/exports/0@lo /proc/fs/lustre/mdt/lustre-MDT0000/exports/0@lo/hash /proc/fs/lustre/mdt/lustre-MDT0000/exports/0@lo/uuid /proc/fs/lustre/mdt/lustre-MDT0000/exports/0@lo/stats /proc/fs/lustre/mdt/lustre-MDT0000/exports/0@lo/export
# proc_regexp="/\{proc,sys}/\{fs,sys,kernel/debug}/\{lustre,lnet}/" # proc_dirs=$(eval ls -d $proc_regexp)
After running the upper commands, 'echo "$proc_dirs"' woud print
multiple lines like what sanity test 401a would print:
proc_dirs='/proc/fs/lustre/ /sys/fs/lustre/ /sys/kernel/debug/lnet/ /sys/kernel/debug/lustre/'
Attachments
Issue Links
- is related to
-
LU-14789 sanity 133f and 133g are no longer effective
- Resolved