[LU-13057] sanity-pcc test_1c: Failed to start copytool ost8 Created: 08/Dec/19  Updated: 12/Dec/19  Resolved: 11/Dec/19

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: Lustre 2.14.0
Fix Version/s: Lustre 2.14.0

Type: Bug Priority: Major
Reporter: Maloo Assignee: Yang Sheng
Resolution: Fixed Votes: 0
Labels: None

Severity: 3
Rank (Obsolete): 9223372036854775807

 Description   

This issue was created by maloo for bfaccini <bruno.faccini@intel.com>

This issue relates to the following test suite run: https://testing.whamcloud.com/test_sets/00bb8e6a-184c-11ea-9487-52540065bddc

test_1c failed with the following error:

Failed to start copytool ost8 on 'onyx-32vm3'

This seems to occur quite frequently with current master.
sanity-pcc/test_[1c,1d,1f,2a,2b,2c,4,13c] have also failed due to the same problem.

On concerned OSS/node, copytool log only contains the following msgs :

lhsmtool_posix: 1575650381.038441 lhsmtool_posix[26981]: action=0 src=(null) dst=(null) mount_point=/mnt/lustre
lhsmtool_posix: '/mnt/lustre' not on a mounted Lustre filesystem
lhsmtool_posix: 1575650381.038826 lhsmtool_posix[26981]: cannot find a Lustre filesystem mounted at '/mnt/lustre': No such device (19)

VVVVVVV DO NOT REMOVE LINES BELOW, Added by Maloo for auto-association VVVVVVV
sanity-pcc test_1c - Failed to start copytool ost8 on 'onyx-32vm3'



 Comments   
Comment by Gerrit Updater [ 09/Dec/19 ]

Yang Sheng (ys@whamcloud.com) uploaded a new patch: https://review.whamcloud.com/36957
Subject: LU-13057 tests: sanity-pcc test_1c: Failed to start copytool
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 190f3362438ad1fc6473ec6c59998fbeca1f1b6b

Comment by Gerrit Updater [ 10/Dec/19 ]

Andreas Dilger (adilger@whamcloud.com) merged in patch https://review.whamcloud.com/36957/
Subject: LU-13057 tests: sanity-pcc test_1c: Failed to start copytool
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: f51895b8dd26ef32af19723610718a6d41a3666c

Generated at Sat Feb 10 02:57:59 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.