[LU-3981] sanity-hsm test_25a failure: 'import of d0.sanity-hsm/d25/f.sanity-hsm.25a to /lustre/scratch/d0.sanity-hsm/d25/f.sanity-hsm.25a failed' Created: 20/Sep/13  Updated: 24/Sep/13  Resolved: 24/Sep/13

Status: Closed
Project: Lustre
Component/s: None
Affects Version/s: Lustre 2.5.0
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: James Nunez (Inactive) Assignee: WC Triage
Resolution: Duplicate Votes: 0
Labels: HSM
Environment:

OpenSFS cluster with combined MGS/MDS, single OSS with two OSTs, four clients; one agent (c07), one with robinhood/db running (c08) and just running as Lustre clients (c09, c10)


Issue Links:
Duplicate
duplicates LU-3979 sanity-hsm test_10a failure: 'archive... Resolved
Severity: 3
Rank (Obsolete): 10616

 Description   

Test results are at https://maloo.whamcloud.com/test_sets/28e49004-2171-11e3-b1f0-52540035b04c

From the client test_log:

== sanity-hsm test 25a: Restore lost file (HS_LOST flag) from import == 10:44:52 (1379526292)
pdsh@c10: c07: ssh exited with exit code 1
Purging archive on c07
Starting copytool agt1 on c07
c07: lhsmtool_posix[2901]: action=1 src=d0.sanity-hsm/d25/f.sanity-hsm.25a dst=/lustre/scratch/d0.sanity-hsm/d25/f.sanity-hsm.25a mount_point=/lustre/scratch
c07: lhsmtool_posix[2901]: cannot opendir '/archive/scratch/d0.sanity-hsm/d25/f.sanity-hsm.25a': No such file or directory (2)
pdsh@c10: c07: ssh exited with exit code 2
 sanity-hsm test_25a: @@@@@@ FAIL: import of d0.sanity-hsm/d25/f.sanity-hsm.25a to /lustre/scratch/d0.sanity-hsm/d25/f.sanity-hsm.25a failed 


 Comments   
Comment by jacques-charles lafoucriere [ 22/Sep/13 ]

import failure, archive backend name wrong or not mounted on agent (seen: "c07: lhsmtool_posix[2901]: cannot opendir '/archive/scratch/d0.sanity-hsm/d25/f.sanity-hsm.25a': No such file or directory (2)")

Comment by James Nunez (Inactive) [ 24/Sep/13 ]

Comment from Jinshan: cp should be running on agent host

Comment by jacques-charles lafoucriere [ 24/Sep/13 ]

duplicate of LU-3979

Generated at Sat Feb 10 01:38:36 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.