Project

General

Profile

Actions
Copy link

Bug #49229

closed

crimson unittests failing 'make check' due to insufficient aio-max-nr

Added by Josh Durgin about 3 years ago. Updated about 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Kefu Chai
Category:
-
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
40568
Crash signature (v1):
Crash signature (v2):

Description

From https://jenkins.ceph.com/job/ceph-pull-requests/68977/

180/215 Test #211: unittest-extmap-manager ...................***Failed    4.02 sec
WARNING: debug mode. Not for benchmarking or production
ERROR 2021-02-09 23:10:01,467 [shard 39] seastar - Could not setup Async I/O: Resource temporarily unavailable. The most common cause is not enough request capacity in /proc/sys/fs/aio-max-nr. Try increasing that number or reducing the amount of logical CPUs available for your application

181/215 Test #210: unittest-seastore-cache ...................***Failed    4.02 sec
WARNING: debug mode. Not for benchmarking or production
ERROR 2021-02-09 23:10:01,479 [shard 40] seastar - Could not setup Async I/O: Resource temporarily unavailable. The most common cause is not enough request capacity in /proc/sys/fs/aio-max-nr. Try increasing that number or reducing the amount of logical CPUs available for your application

182/215 Test #209: unittest-seastore-journal .................***Failed    4.62 sec
WARNING: debug mode. Not for benchmarking or production
ERROR 2021-02-09 23:10:01,464 [shard 43] seastar - Could not setup Async I/O: Resource temporarily unavailable. The most common cause is not enough request capacity in /proc/sys/fs/aio-max-nr. Try increasing that number or reducing the amount of logical CPUs available for your application
Actions
Copy link

Also available in: Atom PDF