Details
-
Bug
-
Resolution: Fixed
-
Minor
-
None
-
None
-
None
-
3
-
9223372036854775807
Description
This issue was created by maloo for S Buisson <sbuisson@ddn.com>
This issue relates to the following test suite run: https://testing.whamcloud.com/test_sets/4824ed24-8a35-468e-b1f1-3e1efcc5321f
test_104c failed with the following error:
test_104c returned 2
The test seems broken.
It ends with:
After recordsize change lfs output : filesystem_summary: 73.0G 150.8M 72.9G 1% /mnt/lustre df output : 10.9.4.19@tcp:/lustre 74G 150M 73G 1% /mnt/lustre CMD: trevis-71vm4 /usr/sbin/lctl get_param -n osd-zfs.lustre-MDT0000..mntdev CMD: trevis-71vm4 zfs set recordsize=131072 lustre-mdt1/mdt1 CMD: trevis-71vm5 /usr/sbin/lctl get_param -n osd-zfs.lustre-MDT0000..mntdev trevis-71vm5: error: get_param: param_path 'osd-zfs/lustre-MDT0000//mntdev': No such file or directory pdsh@trevis-71vm1: trevis-71vm5: ssh exited with exit code 2
But when it succeeds, for instance in https://testing.whamcloud.com/sub_tests/272da434-33ef-44cc-9710-77a6372826e6, what happens is not really different, but the script manages to set recordsize:
After recordsize change lfs output : filesystem_summary: 73.0G 146.8M 72.9G 1% /mnt/lustre df output : 10.9.10.22@tcp:/lustre 74G 147M 73G 1% /mnt/lustre CMD: trevis-209vm14 lctl get_param -n osd-zfs.lustre-MDT0000..mntdev CMD: trevis-209vm14 zfs set recordsize=131072 lustre-mdt1/mdt1 CMD: trevis-209vm15 lctl get_param -n osd-zfs.lustre-MDT0000..mntdev trevis-209vm15: error: get_param: param_path 'osd-zfs/lustre-MDT0000//mntdev': No such file or directory pdsh@trevis-209vm11: trevis-209vm15: ssh exited with exit code 2 CMD: trevis-209vm15 zfs set recordsize=131072
VVVVVVV DO NOT REMOVE LINES BELOW, Added by Maloo for auto-association VVVVVVV
sanity test_104c - test_104c returned 2
Attachments
Issue Links
- is related to
-
LU-14997 Register "stack_trap" for sanity/104c for cleanup
- Reopened