On Sun, 2024-12-15 at 12:42 -0500, Brian J. Murrell via FreeIPA-users wrote: > > Not really seeing any more information in the access log with this > audit log enabled. > > Looking at the disk I/O more granularly, it has definite peaks and > valleys. This is pretty typical for example: > > 12:26:10 PM tps rkB/s wkB/s dkB/s areq-sz aqu- > sz await %util DEV > 12:26:10 PM 1534.40 0.00 18647.20 0.00 12.15 > 1.79 1.16 86.72 var_lib_dirsrv > 12:26:15 PM 1.80 0.00 7.20 0.00 4.00 > 0.02 11.78 2.02 var_lib_dirsrv > 12:26:20 PM 2.40 0.00 9.60 0.00 4.00 > 0.01 4.00 0.96 var_lib_dirsrv > 12:26:25 PM 686.00 0.00 8214.40 0.00 11.97 > 0.98 1.42 49.92 var_lib_dirsrv > 12:26:30 PM 1344.40 0.00 16421.60 0.00 12.21 > 1.53 1.14 77.68 var_lib_dirsrv > 12:26:35 PM 415.80 0.00 4981.60 0.00 11.98 > 0.40 0.95 20.00 var_lib_dirsrv > 12:26:40 PM 3.60 0.00 17.60 0.00 4.89 > 0.01 3.39 1.04 var_lib_dirsrv > 12:26:45 PM 0.00 0.00 0.00 0.00 0.00 > 0.00 0.00 0.00 var_lib_dirsrv > 12:26:50 PM 5.80 0.00 24.80 0.00 4.28 > 0.03 4.69 2.52 var_lib_dirsrv > 12:26:55 PM 0.00 0.00 0.00 0.00 0.00 > 0.00 0.00 0.00 var_lib_dirsrv > 12:27:00 PM 2.40 0.00 8.80 0.00 3.67 > 0.01 4.42 1.00 var_lib_dirsrv > 12:27:05 PM 150.20 0.00 1771.20 0.00 11.79 > 0.20 1.35 10.26 var_lib_dirsrv > > There is no MOD in the access log at 12;26:25-12:26:35 though.
Did any of the additional information shed any more light on why my dirsrv disk is getting hammered with writes? If not, where can we go from here to figure out why this is happening? Cheers, b.
signature.asc
Description: This is a digitally signed message part
-- _______________________________________________ FreeIPA-users mailing list -- freeipa-users@lists.fedorahosted.org To unsubscribe send an email to freeipa-users-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/freeipa-users@lists.fedorahosted.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue