https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195882
--- Comment #8 from rozhuk...@gmail.com ---
(In reply to Mark Johnston from comment #7)
Main problem is that dirty pages does not go to free after if flushed to disk,
and it cause swap usage.
On 10.1 - system can not allocate mem even after system stop write to disk.
Probably now I should count free mem as: free + laundry.
Another bug: I have 6,5 Gb free, program write 6 Gb, rename file and restart
program. Program fail some time later, but system can not flush pages to disk -
no space, and whole time move mem:
...
CPU: 0.0% user, 0.0% nice, 10.5% system, 7.0% interrupt, 82.5% idle
Mem: 1945M Active, 120K Inact, 1537M Laundry, 315M Wired, 199M Buf, 47M Free
...
CPU: 0.0% user, 0.0% nice, 14.3% system, 6.3% interrupt, 79.5% idle
Mem: 2765M Active, 36K Inact, 717M Laundry, 315M Wired, 199M Buf, 48M Free
16 root 49 - 0 72K CPU3 3 12:26 59.96%
[pagedaemon{laundry: dom0}]
...
and eat CPU.
Until file was deleted.
About kernel dump.
I try:
swapoff -a
swapoff: /dev/gptid/0714a812-b98e-11e8-a831-7085c2375722.eli: Cannot allocate
memory
System has 32 Gb RAM, 1,8 Gb in swap and summ of RES all running apps is less
than 20 Gb.
Only after I stop one vbox vm and get 4+gb free mem it work without error.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
