[LU-1843] sanityn test_4 FAIL on OFD + Ldiskfs Created: 06/Sep/12  Updated: 06/May/15  Resolved: 06/May/15

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

Type: Bug Priority: Minor
Reporter: Maloo Assignee: WC Triage
Resolution: Cannot Reproduce Votes: 0
Labels: None

Severity: 3
Rank (Obsolete): 4067

 Description   

This issue was created by maloo for Minh Diep <mdiep@whamcloud.com>

This issue relates to the following test suite run: https://maloo.whamcloud.com/test_sets/2e5162be-f3ce-11e1-9654-52540035b04c.

== sanityn test 4: fstat validation on multiple mount points ============ 05:56:44 (1346417804)
Blocks don't match 1, 0
sanityn test_4: @@@@@@ FAIL: test_4 failed with 1
Trace dump:
= /usr/lib64/lustre/tests/test-framework.sh:3639:error_noexit()
= /usr/lib64/lustre/tests/test-framework.sh:3661:error()
= /usr/lib64/lustre/tests/test-framework.sh:3894:run_one()
= /usr/lib64/lustre/tests/test-framework.sh:3923:run_one_logged()
= /usr/lib64/lustre/tests/test-framework.sh:3797:run_test()
= /usr/lib64/lustre/tests/sanityn.sh:147:main()
Dumping lctl log to /logdir/test_logs/2012-08-31/lustre-reviews-el6-x86_64_8715_-7f30c90b6a70/sanityn.test_4.*.1346417816.log
CMD: client-30vm3,client-30vm4,client-30vm5,client-30vm6.lab.whamcloud.com /usr/sbin/lctl dk > /logdir/test_logs/2012-08-31/lustre-reviews-el6-x86_64_8715_-7f30c90b6a70/sanityn.test_4.debug_log.\$(hostname -s).1346417816.log;
dmesg > /logdir/test_logs/2012-08-31/lustre-reviews-el6-x86_64_8715_-7f30c90b6a70/sanityn.test_4.dmesg.\$(hostname -s).1346417816.log



 Comments   
Comment by Minh Diep [ 06/Sep/12 ]

this might affect 2.3 as well

Comment by Li Wei (Inactive) [ 23/Sep/12 ]

https://maloo.whamcloud.com/test_sets/933c73d0-0495-11e2-bfd4-52540035b04c

This was master with OFD and LDiskFS OSTs.

Comment by Sarah Liu [ 29/Nov/12 ]

Hit the similar issue while this case is interop between 2.3 server and 2.4 client.
https://maloo.whamcloud.com/test_sets/54982682-397f-11e2-9fda-52540035b04c

Comment by Andreas Dilger [ 06/May/15 ]

This bug is almost certainly obsolete.

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