[LU-4469] replay-dual test_15a: FAIL: f.replay-dual.15a-2-0 exists Created: 10/Jan/14  Updated: 09/Jan/20  Resolved: 09/Jan/20

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

Type: Bug Priority: Minor
Reporter: Jian Yu Assignee: Bob Glossman (Inactive)
Resolution: Duplicate Votes: 0
Labels: ssf
Environment:

Lustre build: http://build.whamcloud.com/job/lustre-reviews/20841/
Distro/Arch: SLES11SP3/x86_64 (both server and client, kernel version: 3.0.101-0.8)


Severity: 3
Rank (Obsolete): 12240

 Description   

replay-dual test 15a failed as follows:

Started lustre-MDT0000
CMD: client-9vm1,client-9vm2 PATH=/usr/lib64/lustre/tests:/usr/lib/lustre/tests:/usr/lib64/lustre/tests:/opt/iozone/bin:/opt/iozone/bin:/usr/lib64/mpi/gcc/openmpi/bin:/usr/lib64/lustre/tests/mpi:/usr/lib64/lustre/tests/racer:/usr/lib64/lustre/../lustre-iokit/sgpdd-survey:/usr/lib64/lustre/tests:/usr/lib64/lustre/utils/gss:/usr/lib64/lustre/utils:/usr/bin:/bin:/sbin:/usr/sbin::/sbin:/bin:/usr/sbin: NAME=autotest_config sh rpc.sh wait_import_state_mount FULL mdc.lustre-MDT0000-mdc-*.mds_server_uuid 
client-9vm1: CMD: client-9vm1 lctl get_param -n at_max
client-9vm2: CMD: client-9vm2 lctl get_param -n at_max
client-9vm1: mdc.lustre-MDT0000-mdc-*.mds_server_uuid in FULL state after 0 sec
client-9vm2: mdc.lustre-MDT0000-mdc-*.mds_server_uuid in FULL state after 0 sec
 - unlinked 0 (time 1389251833 ; total 0 ; last 0)
total: 25 unlinks in 0 seconds: inf unlinks/second
 replay-dual test_15a: @@@@@@ FAIL: f.replay-dual.15a-2-0 exists

Maloo report: https://maloo.whamcloud.com/test_sets/e3e6ca96-7989-11e3-a27b-52540035b04c



 Comments   
Comment by Jodi Levi (Inactive) [ 15/Jan/14 ]

Bob,
Would you be able to look at this one also and comment?
Thank you!

Comment by Bob Glossman (Inactive) [ 19/Feb/14 ]

error "client-9vm3: error: readonly: Operation not supported" seen in logs makes it very likely a dup of LU-4470. Fix already landed in master, in flight for b2_5.

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