Bug 206492
| Summary: | System hangs on huge disk activity | ||
|---|---|---|---|
| Product: | Base System | Reporter: | John Freeman <freemjohn> |
| Component: | kern | Assignee: | Bugmeister <bugmeister> |
| Status: | Closed Overcome By Events | ||
| Severity: | Affects Only Me | CC: | chris, freemjohn, marklmi26-fbsd |
| Priority: | --- | ||
| Version: | 10.2-STABLE | ||
| Hardware: | i386 | ||
| OS: | Any | ||
|
Description
John Freeman
2016-01-22 13:10:55 UTC
Before hang - i can see in htop/top that kernel using 100% of CPU0 time, other processes - ~0% use. Looks like livelock or something similar. If you use a swapfile on a file-system/partition that gets a mix of other IO then see Bug 206048 - 11.0-CURRENT -r293227 (and others) arm (rpi2/BeagleBone Black) amd64 etc: swapfile usage hangs; swap partition works for a problem that may apply to 10.x as well when using things like: file=/var/spool/swap/swapfile file=/swap0 --unless those files are on their own file systems/partitions not used for other (used) files. It may be worth testing if the involved 10.x context(s) hang before settling on this sort of placement of the file. One of the comments suggested a command like: stress -d 2 -m 3 --vm-keep was sufficient to show the problem on at least 11.0-CURRENT amd64 contexts. I guess that command is from the port sysutils/stress . It would actually be good to have 10.x comments in Bug 206048 reporting how such testing went if someone tries it. root:~ # cat /etc/fstab # Device Mountpoint FStype Options Dump Pass# /dev/mirror/gm1s1a / ufs rw 0 1 /dev/mirror/gm1s1b none swap sw 1 0 /dev/mirror/gm1s1d /tmp ufs rw 0 1 /dev/mirror/gm1s1e /var ufs rw 0 1 /dev/mirror/gm1s1f /usr ufs rw 0 1 /dev/mirror/gm1s1g /home ufs rw 0 1 /dev/mirror/gm1s1h /mnt ufs rw,noauto 0 2 #/dev/ufs none swap sw 0 0 #/dev/acd0 /cdrom cd9660 ro,noauto 0 0 proc /proc procfs rw 0 0 linproc /compat/linux/proc linprocfs rw 0 0 fdesc /dev/fd fdescfs rw 0 0 Swap not used on any case, 0mb ^Triage: I'm sorry that this PR did not get addressed in a timely fashion. By now, the version that it was created against is long out of support. Please re-open if it is still a problem on a supported version. |
