[LU-10367] FIO Fails to run with libaio Created: 11/Dec/17 Updated: 07/May/20 Resolved: 22/Jan/19 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.10.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Keith Mannthey (Inactive) | Assignee: | Andriy Skulysh |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Environment: |
Lustre 2.10.1 RHEL 7.4 |
||
| Issue Links: |
|
||||||||||||
| Severity: | 3 | ||||||||||||
| Rank (Obsolete): | 9223372036854775807 | ||||||||||||
| Description |
|
While doing some bench marking with FIO is seems libaio is not working with Lustre. FIO can be found here: https://github.com/axboe/fio/ When running with libaio it quickly fails with error messages. A sample FIO configuration file is below: fsync=1 directory=/mnt/lustre direct=1 numjobs=32 ioengine=libaio blocksize=64k readwrite=readwrite size=65536m group_reporting Sample error messages: ..... lustre: Laying out IO file(s) (1 file(s) / 65536MB) fio: io_u error on file /mnt/lustre/lustre.21.0: Unknown error -131072: read offset=0, buflen=65536 fio: io_u error on file /mnt/lustre/lustre.21.0: Unknown error -131072: read offset=65536, buflen=65536 fio: pid=51260, err=-131072/file:io_u.c:1708, func=io_u error, error=Unknown error -131072 ... Removing libaio options allows FIO to run. Fsync and Direct really slow Lustre down but they run. Other tests work as expected. |
| Comments |
| Comment by Homer Li (Inactive) [ 17/Apr/18 ] |
|
Yes, I have the same problem. It 's lustre 2.10.2 + zfs 0.7.3 |
| Comment by Thomas Favre-Bulle (Inactive) [ 24/Apr/18 ] |
|
Hello, I'm having the same problem with 2.10.3. Async IO simply won't work (libaio), directIO are much slower than what we get with 2.7 (same hardware). Any idea where this could come from please? Thank you, |
| Comment by Gerrit Updater [ 26/Nov/18 ] |
|
Andriy Skulysh (c17819@cray.com) uploaded a new patch: https://review.whamcloud.com/33716 |
| Comment by James A Simmons [ 16/Jan/19 ] |
|
Now that the PIO code has been removed is this a problem still? |
| Comment by Andriy Skulysh [ 22/Jan/19 ] |
|
The patch isn't needed after |
| Comment by Peter Jones [ 22/Jan/19 ] |
|
ok - thanks |
| Comment by Aurelien Degremont (Inactive) [ 19/Feb/19 ] |
|
The problem is still present in 2.10 LTS. The provided patch seems to fix it. Could be interesting for 2.10.7? |