From owner-freebsd-amd64@freebsd.org Sat Oct 1 14:31:02 2016 Return-Path: Delivered-To: freebsd-amd64@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 34006C0553D for ; Sat, 1 Oct 2016 14:31:02 +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 23AC91627 for ; Sat, 1 Oct 2016 14:31:02 +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 u91EV0pE068752 for ; Sat, 1 Oct 2016 14:31:02 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-amd64@FreeBSD.org Subject: [Bug 209421] Processes hangs in D state, suspfs or vofflock wchan under FreeBSD 10.X Date: Sat, 01 Oct 2016 14:31:00 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: chris@cretaforce.gr 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: Message-ID: In-Reply-To: References: 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-amd64@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Oct 2016 14:31:02 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D209421 --- Comment #1 from chris@cretaforce.gr --- Same issue here. It happens randomly, for example during tar, or rsync: procstat -kk 66610 PID TID COMM TDNAME KSTACK 66610 101290 bsdtar - mi_switch+0xe1 sleepq_wait+0= x3a _sleep+0x287 vnode_create_vobject+0x100 ufs_open+0x6d VOP_OPEN_APV+0xa1 vn_open_vnode+0x234 vn_open_cred+0x36a kern_openat+0x26f amd64_syscall+0x40f Xfast_syscall+0xfb fstat -p 66610 USER CMD PID FD MOUNT INUM MODE SZ|DV R/W root bsdtar 66610 text /usr 903274 -r-xr-xr-x 58392 r root bsdtar 66610 wd - 290045184 d--------- 512 r root bsdtar 66610 root / 2 drwxr-xr-x 512 r root bsdtar 66610 0* pipe fffff804efe05000 <-> fffff804efe05160= =20=20=20=20=20 0 rw root bsdtar 66610 1* pipe fffff8000e2d1730 <-> fffff8000e2d15d0= =20=20=20=20=20 0 rw root bsdtar 66610 2* pipe fffff804e9480448 <-> fffff804e94802e8= =20=20=20=20=20 0 rw root bsdtar 66610 3 - 290045184 d--------- 512 r root bsdtar 66610 4 - 293018454 drwxr-xr-x 15111168 r root bsdtar 66610 5 - 293018454 drwxr-xr-x 15111168 r --=20 You are receiving this mail because: You are on the CC list for the bug.=