[LU-10468] sanity-flr test_21: i_blocks error expected Created: 08/Jan/18  Updated: 14/Jan/18  Resolved: 13/Jan/18

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

Type: Bug Priority: Minor
Reporter: Maloo Assignee: Jinshan Xiong (Inactive)
Resolution: Fixed Votes: 0
Labels: None

Severity: 3
Rank (Obsolete): 9223372036854775807

 Description   

sanity-flr test_21 - 'i_blocks error expected: 1, actual: 15364'
^^^^^^^^^^^^^ DO NOT REMOVE LINE ABOVE ^^^^^^^^^^^^^

This issue was created by maloo for sarah_lw <wei3.liu@intel.com>

This issue relates to the following test suite run:

test_21 failed with the following error:

'i_blocks error expected: 1, actual: 15364'

This error has been seen on master EL7 ZFS configs
test log

== sanity-flr test 21: glimpse should report accurate i_blocks ======================================= 07:08:34 (1515222514)
15+0 records in
15+0 records out
15728640 bytes (16 MB) copied, 0.0143849 s, 1.1 GB/s
1+0 records in
1+0 records out
1048576 bytes (1.0 MB) copied, 0.00221288 s, 474 MB/s
 sanity-flr test_21: @@@@@@ FAIL: i_blocks error expected: 1, actual: 15364 


 Comments   
Comment by Jinshan Xiong (Inactive) [ 10/Jan/18 ]

I just set up a test env locally, and I couldn't reproduce this problem. Sara will set up a testing env and reproduce it. Let's see how it goes.

Comment by Gerrit Updater [ 11/Jan/18 ]

Jinshan Xiong (jinshan.xiong@intel.com) uploaded a new patch: https://review.whamcloud.com/30828
Subject: LU-10468 tests: sync zfs dataset before reading blocks
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 78687d226dfa9e54a89e9e3ab821f10373fb91a7

Comment by Gerrit Updater [ 13/Jan/18 ]

Oleg Drokin (oleg.drokin@intel.com) merged in patch https://review.whamcloud.com/30828/
Subject: LU-10468 tests: sync zfs dataset before reading blocks
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: 5e29a919c39eee9dacbf7d8b06348b5296b79cd2

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