[Bug 277717] kernel using 100% CPU in arc_prune in 13.3

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277717

--- Comment #8 from Trev <fbsdbugs4@sentry.org> ---
FreeBSD 13.3-STABLE #4 stable/13-b5e7969b2: Fri Mar 29 20:50:35 AEDT 2024
- The system now locks up more or less every second day during the backup
process using ZFS send to send a ZFS snapshot to an external UFS hard disk
attached via USB. It is only every second day (more or less) that arc_prune is
consuming 100% of one CPU core and the two things always occur together (ie
arc_prune running amok and the system freezing).

Mar 31 06:00:00 shadow kernel: umass0: <Seagate GoFlex Desk, class 0/0, rev
2.10/1.00, addr 4> on usbus3
Mar 31 06:00:00 shadow kernel: da0 at umass-sim0 bus 0 scbus3 target 0 lun 0
Mar 31 06:00:00 shadow kernel: da0: <Seagate GoFlex Desk 0D19> Fixed Direct
Access SPC-3 SCSI device
Mar 31 06:00:00 shadow kernel: da0: Serial Number NA0MBZV8
Mar 31 06:00:00 shadow kernel: da0: 40.000MB/s transfers
Mar 31 06:00:00 shadow kernel: da0: 2861588MB (732566645 4096 byte sectors)
Mar 31 06:00:00 shadow kernel: da0: quirks=0x2<NO_6_BYTE>
Mar 31 06:00:30 shadow root[42531]: Start local backup to da0p1
Mar 31 06:34:38 shadow kernel: pid 62306 (seamonkey), jid 0, uid 1001, was
killed: a thread waited too long to allocate a page
Mar 31 06:37:17 shadow kernel: pid 26160 (smbd), jid 0, uid 0, was killed: a
thread waited too long to allocate a page
Mar 31 06:38:30 shadow kernel: pid 26033 (named), jid 0, uid 53, was killed: a
thread waited too long to allocate a page
Mar 31 06:38:54 shadow kernel: pid 26288 (Xorg), jid 0, uid 0, was killed: a
thread waited too long to allocate a page
Mar 31 07:14:12 shadow kernel: pid 26214 (milter-greylist), jid 0, uid 26, was
killed: a thread waited too long to allocate a page
Mar 31 07:14:12 shadow kernel: pid 26268 (tcsh), jid 0, uid 1001, was killed: a
thread waited too long to allocate a page
Mar 31 07:14:12 shadow kernel: pid 26167 (milter-relay), jid 0, uid 26, was
killed: a thread waited too long to allocate a page
Mar 31 07:14:12 shadow kernel: pid 26110 (milter-regex), jid 0, uid 26, was
killed: a thread waited too long to allocate a page
Mar 31 07:14:12 shadow kernel: pid 39982 (sendmail), jid 0, uid 0, was killed:
a thread waited too long to allocate a page
Mar 31 07:14:12 shadow kernel: pid 40057 (httpd), jid 0, uid 80, was killed: a
thread waited too long to allocate a page
Mar 31 07:14:12 shadow kernel: pid 40000 (httpd), jid 0, uid 80, was killed: a
thread waited too long to allocate a page
Mar 31 07:14:12 shadow kernel: pid 40054 (httpd), jid 0, uid 80, was killed: a
thread waited too long to allocate a page
Mar 31 07:14:12 shadow kernel: pid 42492 (sendmail), jid 0, uid 25, was killed:
a thread waited too long to allocate a page
Mar 31 07:14:12 shadow kernel: pid 40056 (httpd), jid 0, uid 80, was killed: a
thread waited too long to allocate a page
Mar 31 07:14:12 shadow kernel: pid 40001 (httpd), jid 0, uid 80, was killed: a
thread waited too long to allocate a page
Mar 31 07:14:12 shadow kernel: pid 39999 (httpd), jid 0, uid 80, was killed: a
thread waited too long to allocate a page
Mar 31 07:14:12 shadow kernel: pid 39998 (httpd), jid 0, uid 80, was killed: a
thread waited too long to allocate a page
Mar 31 07:14:12 shadow kernel: pid 43308 (zfs), jid 0, uid 0, was killed: a
thread waited too long to allocate a page
Mar 31 07:14:12 shadow kernel: pid 39996 (sendmail), jid 0, uid 25, was killed:
a thread waited too long to allocate a page
Mar 31 07:14:12 shadow kernel: pid 26092 (ntpd), jid 0, uid 0, was killed: a
thread waited too long to allocate a page

after which the only way to regain access to the server is to turn the power
off :(

-- 
You are receiving this mail because:
You are the assignee for the bug.