From owner-freebsd-current@FreeBSD.ORG Mon Oct 14 13:00:52 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id A6BA86E7 for ; Mon, 14 Oct 2013 13:00:52 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-annu.net.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id 6D56C2568 for ; Mon, 14 Oct 2013 13:00:51 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AqQEACrqW1KDaFve/2dsb2JhbABZgz9Sgym9eUuBOHSCJQEBAQMBAQEBICsgCwUWDgoCAg0ZAikBCSYGCAcEARwEh18GDKsmkjGBKYxwgQU0B4JqgTkDlTqDepBTg0AgMYEDOQ X-IronPort-AV: E=Sophos;i="4.93,492,1378872000"; d="scan'208";a="59217229" Received: from muskoka.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.222]) by esa-annu.net.uoguelph.ca with ESMTP; 14 Oct 2013 09:00:45 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 43140B403B; Mon, 14 Oct 2013 09:00:45 -0400 (EDT) Date: Mon, 14 Oct 2013 09:00:45 -0400 (EDT) From: Rick Macklem To: Allan Jude Message-ID: <2030585715.40821095.1381755645240.JavaMail.root@uoguelph.ca> In-Reply-To: <525B2967.9060404@allanjude.com> Subject: Re: Process stuck in D+ state MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Originating-IP: [172.17.91.201] X-Mailer: Zimbra 7.2.1_GA_2790 (ZimbraWebClient - FF3.0 (Win)/7.2.1_GA_2790) Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Oct 2013 13:00:52 -0000 Allan Jude wrote: > On 2013-10-13 15:10, Olivier Cochard-Labb=C3=A9 wrote: > > I've got a frequent problem on my desktop (FreeBSD 10.0-ALPHA5 #8 > > r256200): > > After few hours I can't acces to one of my folder: A simple "ls" in > > this folder stucks, and all filesystem information started after > > (df, > > fstat) stuck too in D+. > > > > SIGINFO report this usage for these processes: > > > > load: 0.15 cmd: ls 15716 [rpcrecon] 217.89r 0.00u 0.00s 0% 2440k > > load: 0.34 cmd: ls 15716 [connec] 2376.60r 0.00u 0.00s 0% 0k > > load: 0.40 cmd: ls 15716 [connec] 2379.80r 0.00u 0.00s 0% 0k > > load: 0.40 cmd: ls 15716 [connec] 2379.92r 0.00u 0.00s 0% 0k > > load: 0.37 cmd: ls 15716 [rpcrecon] 2850.26r 0.00u 0.00s 0% 0k > > load: 0.37 cmd: ls 15716 [rpcrecon] 2850.39r 0.00u 0.00s 0% 0k > > > > load: 0.40 cmd: fstat 15781 [rpcrecon] 2842.08r 0.00u 0.01s 0% 0k > > load: 0.21 cmd: fstat 15781 [rpcrecon] 2879.35r 0.00u 0.01s 0% 0k > > load: 0.21 cmd: fstat 15781 [rpcrecon] 2879.48r 0.00u 0.01s 0% 0k > > load: 0.21 cmd: fstat 15781 [rpcrecon] 2879.63r 0.00u 0.01s 0% 0k > > > > load: 0.24 cmd: df 15919 [connec] 1047.98r 0.00u 0.00s 0% 0k > > load: 0.22 cmd: df 15919 [connec] 1054.22r 0.00u 0.00s 0% 0k > > > > and the PS status: > > > > olivier 15919 0.0 0.0 14400 16 7 D+ 7:06PM > > 0:00.01 df -h > > olivier 15781 0.0 0.0 20708 16 6 D+ 6:26PM > > 0:00.02 fstat > > olivier 15651 0.0 0.0 16784 16 4 D+ 6:25PM > > 0:00.00 ls > > > > My desktop use a geli system and JSU, nothing special, here are the > > mount point: > > /dev/ada1p3.eli on / (ufs, local, noatime, journaled soft-updates) > > devfs on /dev (devfs, local, multilabel) > > /dev/gpt/boot on /boot2 (ufs, local, noatime, soft-updates) > > > > What kind of commands can I use for getting more troubleshooting( > > information next time ? > > > > Thanks > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to > > "freebsd-current-unsubscribe@freebsd.org" > Looking at the process states, connect and rpcreconnect, seem to > suggest > something involving yp/nis or NFS or some such. >=20 Yea. I don't think yp/nis uses the kernel rpc. All I can think of is that you either have an NFS entry in your /etc/fstab or an amd mapped mount point. rpc.lockd also uses the kernel rpc, but I can't think of how it would become actiev without an NFS mount. (rpcrecon and connec suggest the kernel RPC is trying to (re)connect via TCP to an NFS server) Good luck with it, rick > try: ls -n (skip uid to symbolic name lookup) and see if it behaves > any > differently > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org" >=20