From owner-freebsd-bugs@freebsd.org Mon Jul 24 16:33:23 2017 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 246DDCFE107 for ; Mon, 24 Jul 2017 16:33:23 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0F64F6E810 for ; Mon, 24 Jul 2017 16:33:23 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v6OGXMHR067847 for ; Mon, 24 Jul 2017 16:33:22 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 220971] Freebsd 11.0p11 - system freeze on intensive I/O Date: Mon, 24 Jul 2017 16:33:23 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: execve@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jul 2017 16:33:23 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D220971 Bug ID: 220971 Summary: Freebsd 11.0p11 - system freeze on intensive I/O Product: Base System Version: 11.0-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: execve@gmail.com Hi, I am duplicating my text from email to freebsd-questions and also indicating clues from my investigation so far. I came back to using FreeBSD after many years on my laptop. The machine is currently in a dual-boot configuration and I basically replaced FreeBSD to replace the earlier Ubuntu installation. Machine is at 11.0-RELEASE updated= to p11 via freebsd-update. I encountered a similar outcome of total system freeze in two kinds of usag= e. State of the system: 1) X is not usable - I use xfce - no login manager 2) I cannot ssh into the box - I do not get the username or password prompt= - connection just times out 3) the network interface is ping-able.=20 4) I am not able to switch to the system consoles using Ctrl-Alt-F1..8 5) No mouse movement nor screen update 6) I suspected an issue with soft-update and then turned that off. Filesyst= em is ufs. fsck is clean.=20 Recovery: hard-boot, system comes up, fsck happens, some errors fixed and resumes working normally. The problem became visible in two kind of usage scenarios: 1) Running the backup port duplicity to create a backup of the / filesystem= . It would start but at some point but then get stuck. Running it in verbose mode would sometimes indicate that this would happen when the write to the volume (default setting of 200M) happens. This was tried 4-5 times.=20 2) running split on a 6.4G file (filesystem dump of disk using dump) -- something like=20 split -d -b 200M -a 4 - part=20 This would then freeze at one point - making the system unusable. I tried t= his 2-3 times.=20 I finally got it to work using idprio 31 before the split command. Tried th= is only once - havent tried it with the duplicity command.=20 The machine has 8GB RAM and is clearly not reaching the out of memory kind = of situation - basically only about 1.1 or so GB is used.=20 I also ran this from the system console without X and faced the same issue = - no panic message - nothing in the logs as well. I got a clue from my further searching on the freebsd mailing lists and for= ums. It has to do with the swap file. =E2=80=8BI dont have a swap partition sinc= e I just put the freebsd root over the ubuntu partition. And I had created a=20 swap file based on the instructions in 11.12.2 Creating a swap file. https://www.freebsd.org/doc/handbook/adding-swap-space.html I got a clue from the freebsd-forums: https://forums.freebsd.org/threads/58266/ If the link is down (for some reason, I see the server is down quite often these days), use the below cached link: https://webcache.googleusercontent.com/search?q=3Dcache:y1bJLmSEjWUJ:https:= //forums.freebsd.org/threads/58266/+&cd=3D2&hl=3Den&ct=3Dclnk&gl=3Din So, I just did a swapoff -La and then ran the split command again - no issu= es whatsover!=20 Some idea about the configuration can be had by looking at the information below; please let me know if any further logs / debugging information neede= d. $ freebsd-version=20 11.0-RELEASE-p11 $ uname -a FreeBSD mellon 11.0-RELEASE-p9 FreeBSD 11.0-RELEASE-p9 #0: Tue Apr 11 08:48= :40 UTC 2017 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERI= C=20 amd64 CPU: Intel(R) Core(TM) i3-2330M CPU @ 2.20GHz (2195.06-MHz K8-class CPU) Origin=3D"GenuineIntel" Id=3D0x206a7 Family=3D0x6 Model=3D0x2a Steppi= ng=3D7 =20 Features=3D0xbfebfbff =20 Features2=3D0x1dbae3bf AMD Features=3D0x28100800 AMD Features2=3D0x1 XSAVE Features=3D0x1 VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID TSC: P-state invariant, performance statistics real memory =3D 8589934592 (8192 MB) avail memory =3D 8172896256 (7794 MB) --=20 You are receiving this mail because: You are the assignee for the bug.=