AIX: lio_listio returned EAGAIN

最新推荐文章于 2022-03-31 22:25:52 发布
原创 最新推荐文章于 2022-03-31 22:25:52 发布 · 316 阅读 · 0 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
文章标签：

#数据库

本文探讨了Oracle数据库中出现的警告信息“lio_listio返回EAGAIN”，并解释了这一现象背后的原因及可能的性能影响。文章还提供了IBM官方对此警告的解释，并给出了调整参数maxreqs的具体建议。

摘要生成于 C知道 ，由 DeepSeek-R1 满血版支持， 前往体验 >

最近观察到数据库服务器 $BDUMP 目录下频繁出现 Trace 文件,内容大致为:

Warning: lio_listio returned EAGAIN
Performance degradation may be seen.
Warning: lio_listio returned EAGAIN
Performance degradation may be seen.
Warning: lio_listio returned EAGAIN

搜索了一下, IBM 给的官方解释为:

If the maxreqs value is too low, then the following Oracle warning message might be returned:
Warning: lio_listio returned EAGAIN.
This warning message indicates a need to increase the maxreqs value. When performing file system I/O, a maxservers value that is too low can also indirectly cause this warning message


同时,建议

maxservers=(10 * number of logical disks / number of processors)

AIO Servers ,指的是处理异步IO请求的核心进程.
关于 AIO Servers , 如果要深究，还有许多内容可以讨论。有时间的话把其他内容补充上来.

Google+
Fenng
关注
激光里程计：lio-sam复现
如果想成为中心，那么就到中心去吧。
08-18 588
在LIO-SAM/include/utility.h文件中进行修改。改正utility.h中的引用排序。
Warning: lio_listio returned EAGAIN Performance degradation may be seen
weixin_34112208的博客
10-24 107
Warning: lio_listio returned EAGAIN Performance degradation may be seen. WARNING:Oracle process running out of OS kernel I/O resources (1) 出现以上信息一般代表AIX 的AIO参数配置不是最佳，可能导致Oracle IO性能下降， ...
oracle数据库报lio_listio returned EAGAIN警告
conghan5328的博客
03-28 132
在AIX上会发生，调整操作系统的aio参数 minservers=10=maxservers/2 maxservers=20 maxrequest=8192 类别：Oracle查看评论Link ...
AIX 系统Warning: I/O request got either EINTR or EAGAIN
congtudi4111的博客
10-21 2118
ORACLE 后台警告： *** SESSION ID:(84.64927) 2008-10-21 02:16:37.578Warning: I/O request got either EINTR or EAGAINWarn...
异步IO
老鹏
09-08 912
介绍 IO 的异步 AIO
投资组合：Bem-vindo ao projeto do meuportfólio:man_light_skin_tone:‍:man_light_skin_tone:
02-05
Bem-vindo ao projeto do meuportfólio:man_technologist_light_skin_tone: :briefcase: ·报告程序· nd迪斯 原始的灵魂 :information: 住宅的外观设计和外观设计，以及房屋装修。 Construido ...
olcon build Starting >>> lio_sam --- stderr: lio_sam CMake Error at CMakeLists.txt:10 (find_package): By not providing "Findcatkin.cmake" in CMAKE_MODULE_PATH this project has asked CMake to find a package configuration file provided by "catkin", but CMake did not find one. Could not find a package configuration file provided by "catkin" with any of the following names: catkinConfig.cmake catkin-config.cmake Add the installation prefix of "catkin" to CMAKE_PREFIX_PATH or set "catkin_DIR" to a directory containing one of the above files. If "catkin" provides a separate development package or SDK, be sure it has been installed. --- Failed <<< lio_sam [0.25s, exited with code 1] Summary: 0 packages finished [0.48s] 1 package failed: lio_sam 1 package had stderr output: lio_sam
07-01
我们正在处理一个关于在构建LIO-SAM时遇到的CMake错误：无法找到catkinConfig.cmake文件。根据引用[2]中的错误信息，错误发生在CMake尝试在指定路径`/opt/ros/noetic/share/catkin/cmake/catkinConfig.cmake`处查找...
colcon build --symlink-install Starting >>> lio_sam --- stderr: lio_sam CMake Warning (dev) at CMakeLists.txt:29 (find_package): Policy CMP0074 is not set: find_package uses <PackageName>_ROOT variables. Run "cmake --help-policy CMP0074" for policy details. Use the cmake_policy command to set the policy and suppress this warning. CMake variable PCL_ROOT is set to: /usr For compatibility, CMake is ignoring the variable. This warning is for project developers. Use -Wno-dev to suppress it. CMake Error at CMakeLists.txt:30 (find_package): By not providing "FindGTSAM.cmake" in CMAKE_MODULE_PATH this project has asked CMake to find a package configuration file provided by "GTSAM", but CMake did not find one. Could not find a package configuration file provided by "GTSAM" with any of the following names: GTSAMConfig.cmake gtsam-config.cmake Add the installation prefix of "GTSAM" to CMAKE_PREFIX_PATH or set "GTSAM_DIR" to a directory containing one of the above files. If "GTSAM" provides a separate development package or SDK, be sure it has been installed. --- Failed <<< lio_sam [2.16s, exited with code 1] Summary: 0 packages finished [2.40s] 1 package failed: lio_sam 1 package had stderr output: lio_sam
07-01
我们正在解决在ROS2 Humble中构建lio_sam包时出现的CMake错误，特别是关于GTSAM和PCL_ROOT的警告与错误。根据用户的问题，主要涉及两个问题：1.find_package找不到GTSAM2.关于PCL_ROOT的警告同时，用户还提供了引用...
ubuntu@aimo-master:~/workspace/slam_map/install$ source setup.bash ubuntu@aimo-master:~/workspace/slam_map/install$ roslaunch lio_sam run.launch ... logging to /home/ubuntu/.ros/log/a20c91e0-6b8b-11f0-a519-0007328879dc/roslaunch-aimo-master-11741.log Checking log directory for disk usage. This may take a while. Press Ctrl-C to interrupt WARNING: disk usage in log directory [/home/ubuntu/.ros/log] is over 1GB. It's recommended that you use the 'rosclean' command. xacro: in-order processing became default in ROS Melodic. You can drop the option. started roslaunch server http://aimo-master:34233/ SUMMARY ======== PARAMETERS * /ekf_gps/base_link_frame: base_link * /ekf_gps/frequency: 100 * /ekf_gps/imu0: /imu * /ekf_gps/imu0_config: [False, False, Fa... * /ekf_gps/imu0_differential: False * /ekf_gps/imu0_queue_size: 50 * /ekf_gps/imu0_remove_gravitational_acceleration: True * /ekf_gps/map_frame: map * /ekf_gps/odom0: odometry/gps * /ekf_gps/odom0_config: [True, True, True... * /ekf_gps/odom0_differential: False * /ekf_gps/odom0_queue_size: 10 * /ekf_gps/odom_frame: odom * /ekf_gps/process_noise_covariance: [1.0, 0, 0, 0, 0,... * /ekf_gps/publish_tf: False * /ekf_gps/sensor_timeout: 0.01 * /ekf_gps/two_d_mode: False * /ekf_gps/world_frame: odom * /lio_sam/Horizon_SCAN: 1800 * /lio_sam/N_SCAN: 16 * /lio_sam/baselinkFrame: base_link * /lio_sam/basex: 0.0 * /lio_sam/basey: 0.0 * /lio_sam/basez: 0.0 * /lio_sam/downsampleRate: 1 * /lio_sam/edgeFeatureMinValidNum: 10 * /lio_sam/edgeThreshold: 1.0 * /lio_sam/extrinsicRPY: [1, 0, 0, 0, 1, 0... * /lio_sam/extrinsicRot: [1, 0, 0, 0, 1, 0... * /lio_sam/extrinsicTrans: [0, 0.0, 0.0] * /lio_sam/globalMapVisualizationLeafSize: 1.0 * /lio_sam/globalMapVisualizationPoseDensity: 10.0 * /lio_sam/globalMapVisualizationSearchRadius: 1000.0 * /lio_sam/gpsCovThreshold: 0.25 * /lio_sam/gpsTopic: /gps_odom * /lio_sam/historyKeyframeFitnessScore: 0.3 * /lio_sam/historyKeyframeSearchNum: 50 * /lio_sam/historyKeyframeSearchRadius: 15.0 * /lio_sam/historyKeyframeSearchTimeDiff: 60.0 * /lio_sam/imuAccBiasN: 0.000668232277397 * /lio_sam/imuAccNoise: 0.0127916818168 * /lio_sam/imuGravity: 9.80511 * /lio_sam/imuGyrBiasN: 4.43906245089e-05 * /lio_sam/imuGyrNoise: 0.000924516165897 * /lio_sam/imuRPYWeight: 0.01 * /lio_sam/imuTopic: /imu * /lio_sam/lidarFrame: base_link * /lio_sam/lidarMaxRange: 1000.0 * /lio_sam/lidarMinRange: 1.0 * /lio_sam/loopClosureEnableFlag: True * /lio_sam/loopClosureFrequency: 1.0 * /lio_sam/mapFrame: map * /lio_sam/mappingCornerLeafSize: 0.2 * /lio_sam/mappingProcessInterval: 0.15 * /lio_sam/mappingSurfLeafSize: 0.4 * /lio_sam/numberOfCores: 16 * /lio_sam/odomTopic: /odometry/imu * /lio_sam/odometryFrame: odom * /lio_sam/odometrySurfLeafSize: 0.4 * /lio_sam/pointCloudTopic: /velodyne_points * /lio_sam/poseCovThreshold: 0.05 * /lio_sam/rotation_tollerance: 0.05 * /lio_sam/savePCD: True * /lio_sam/savePCDDirectory: /workspace/pcdmap/ * /lio_sam/sensor: velodyne * /lio_sam/surfFeatureMinValidNum: 100 * /lio_sam/surfThreshold: 0.1 * /lio_sam/surroundingKeyframeDensity: 2.0 * /lio_sam/surroundingKeyframeSearchRadius: 50.0 * /lio_sam/surroundingKeyframeSize: 50 * /lio_sam/surroundingkeyframeAddingAngleThreshold: 0.2 * /lio_sam/surroundingkeyframeAddingDistThreshold: 1.0 * /lio_sam/useGpsElevation: False * /lio_sam/useImuHeadingInitialization: True * /lio_sam/z_tollerance: 0.5 * /navsat/broadcast_utm_transform: False * /navsat/broadcast_utm_transform_as_parent_frame: False * /navsat/delay: 0.0 * /navsat/frequency: 100 * /navsat/magnetic_declination_radians: 0 * /navsat/publish_filtered_gps: False * /navsat/wait_for_datum: False * /navsat/yaw_offset: 0 * /navsat/zero_altitude: True * /passthrough/filter_field_name: y * /passthrough/filter_limit_negative: True * /robot_description: <?xml version="1.... * /rosdistro: melodic * /rosversion: 1.14.13 * /use_sim_time: True NODES / lio_sam_featureExtraction (lio_sam/lio_sam_featureExtraction) lio_sam_imageProjection (lio_sam/lio_sam_imageProjection) lio_sam_imuPreintegration (lio_sam/lio_sam_imuPreintegration) lio_sam_mapOptmization (lio_sam/lio_sam_mapOptmization) lio_sam_rviz (rviz/rviz) passthrough (nodelet/nodelet) pcl_manager (nodelet/nodelet) robot_state_publisher (robot_state_publisher/robot_state_publisher) auto-starting new master process[master]: started with pid [11756] ROS_MASTER_URI=http://aimo-master:11311 setting /run_id to a20c91e0-6b8b-11f0-a519-0007328879dc process[rosout-1]: started with pid [11767] started core service [/rosout] process[pcl_manager-2]: started with pid [11774] process[passthrough-3]: started with pid [11775] RLException: Unable to launch [lio_sam_imuPreintegration-4]. If it is a script, you may be missing a '#!' declaration at the top. The traceback for the exception was written to the log file [ INFO] [1753690792.303750132]: Loading nodelet /passthrough of type pcl/PassThrough to manager pcl_manager with the following remappings: [ INFO] [1753690792.304784038]: /passthrough/input -> /driver/velodyne_points [ INFO] [1753690792.304812513]: /passthrough/output -> /velodyne_points [ INFO] [1753690792.307411190]: waitForService: Service [/pcl_manager/load_nodelet] has not been advertised, waiting... [ INFO] [1753690792.320529335]: Initializing nodelet with 8 worker threads. [lio_sam_imuPreintegration-4] killing on exit [passthrough-3] killing on exit [pcl_manager-2] killing on exit [rosout-1] killing on exit [master] killing on exit
最新发布
07-29
首先，用户的问题是关于启动LIO-SAM系统时遇到的错误：运行`roslaunch lio_sam run.launch`时出现`RLException: Unable to launch lio_sam_imuPreintegration-4`。用户需要帮助定位并解决这个异常原因。 从系统级...
4-POSIX 异步IO(批量请求)
Lawrence_121
09-02 782
POSIX 提供了函数 lio_listio 可以让我们一次性发起多个异步 IO 请求。 1. lio_listio (1) 函数原型 int lio_listio(int mode, struct aiocb *const aiocb_list[], int nitems, struct sigevent *sevp); (2) 函数参数 mode mode 有两个可选值：LIO_W...
126-POSIX 异步IO（批量请求）
进击的小学生
03-29 1640
POSIX 提供了函数 lio_listio 可以让我们一次性发起多个异步 IO 请求。1. lio_listio(1) 函数原型int lio_listio(int mode, struct aiocb *const aiocb_list[], int nitems, struct sigevent *sevp);(2) 函数参数 mode mode 有两个可选值：LIO_WAIT 和 LIO_N
linux IO模型与AIO
secretx的专栏
12-15 3563
AIO 简介 Linux 异步 I/O 是 Linux 内核中提供的一个相当新的增强。它是 2.6 版本内核的一个标准特性，但是我们在 2.4 版本内核的补丁中也可以找到它。AIO 背后的基本思想是允许进程发起很多 I/O 操作，而不用阻塞或等待任何操作完成。稍后或在接收到 I/O 操作完成的通知时，进程就可以检索 I/O 操作的结果。 I/O 模型 在深入介绍 AIO API
Linux系统编程(十)--高级IO-异步IO
桑凯旋的博客
03-31 1828
文章目录1 同步IO与异步IO2 POSIX异步IO（aiocb）3 异步操作状态3.1 aio_error3.2 aio_return4 等待异步IO操作5 异步IO取消操作6 批量请求7 异步通知7.1 两种通知方式7.2 aiocb的成员aio_sigevent7.3 sigevent 的成员 1 同步IO与异步IO 塞和非阻塞 从简单的开始，我们以经典的读取文件的模型举例。（对操作系统而言，所有的输入输出设备都被抽象成文件。） 在发起读取文件的请求时，应用层会调用系统内核的I/O接口。 如果应用层调
linux下aio异步读写详解与实例
乐于分享
11-12 1202
1.为什么会有异步I/O aio异步读写是在linux内核2.6之后才正式纳入其标准。之所以会增加此模块，是因为众所周知我们计算机CPU的执行速度远大于I/O读写的执行速度，如果我们用传统的阻塞式或非阻塞式来操作I/O的话，那么我们在同一个程序中(不用多线程或多进程)就不能同时操作俩个以上的文件I/O，每次只能对一个文件进行I/O操作，很明显这样效率很低下(因为CPU速度远大于I/O操作的速度，所以当执行I/O时，CPU其实还可以做更多的事)。因此就诞生了相对高效的异步I/O 2.异步I/O的基本概念
POSIX 异步IO介绍
游戏开发
03-04 2649
POSIX.1b定义了一系列新的IO操作，能较大地减少应用程序的IO等待时间。这些新函数允许应用程序发起一个或多个IO操作请求后立即返回做其他事情不必等到IO完成，IO操作可以跟应用程序并行执行。AIO控制块 struct aiocb 描述：int aio_fildes        需要操作的文件描述符，所关联的文件必须能支持seek操作。像pipe、socket等设备不能使用aio。off_t
linux异步io 回调函数,Linux异步IO
weixin_42099151的博客
05-07 772
Linux中最常用的IO模型是同步IO，在这个模型中，当请求发出之后，应用程序就会阻塞，直到请求满足条件为止。这是一种很好的解决方案，调用应用程序在等待IO完成的时候不需要占用CPU，但是在很多场景中，IO请求可能需要和CPU消耗交叠，以充分利用CPU和IO提高吞吐率。下图描绘了异步IO的时序，应用程序发起IO操作后，直接开始执行，并不等待IO结束，它要么过一段时间来查询之前的IO请求完成情况，要...
慢慢聊Linux AIO
热门推荐
薛正华的专栏
03-12 2万+
参考： https://www.google.com.hk/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&ved=0CCcQFjAA&url=http://blog.youkuaiyun.com/gotosola/article/details/7412409&ei=ZZEMU-LGCoLeigfW7YHwAw&usg=AFQjCNHCEu63dnM-i77SfSECvq
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值