From owner-freebsd-stable@FreeBSD.ORG Sat May 22 09:42:50 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6924316A4CE for ; Sat, 22 May 2004 09:42:50 -0700 (PDT) Received: from auk2.snu.ac.kr (auk2.snu.ac.kr [147.46.100.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id EF5F143D1F for ; Sat, 22 May 2004 09:42:49 -0700 (PDT) (envelope-from stopspam@users.sourceforge.net) Received: from [147.46.44.181] (stopspam@users.sourceforge.net) by auk2.snu.ac.kr (Terrace Internet Messaging Server) with ESMTP id 2004052301:25:29:802076.13435.2832972720 for ; Sun, 23 May 2004 01:25:29 +0900 (KST) Message-ID: <40AF82F9.4010409@users.sourceforge.net> Date: Sun, 23 May 2004 01:42:33 +0900 From: Rob User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040507 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <40AB4E3A.6030407@users.sourceforge.net> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-TERRACE-SPAMMARK: NO (SR:13.90) (by Terrace) Subject: Re: system command hangs (unkillable); ps shows 'sbwait' state? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 May 2004 16:42:50 -0000 Robert Watson wrote: > On Wed, 19 May 2004, Rob wrote: > > >>1. I had a 2.5 Gb disk mounted on /home/software. >> As root, I overloaded the filesystem, with negative percentage left >> on the device (from df command). So as root, I did a 'rm -rf' in >> /home/software, followed by a 'df -h'. But the df command gave no >> response and became unkillable by any means (ctrl-C, kill -9 ). >> Using 'ps', I found the df command in the 'sbwait' state. >> >>2. I had a usb device mounted as /dev/da0s1 on /mnt. Mounting (as root) >> went all well, but when I unmounted it, as root, the umount command >> hanged, again the umount command was in sbwait state. >> In this case it was even worse: when I killed the xterminal >> where the umount command was hanging, the whole system froze. >> Only power off/on helped me out here. >> >>I don't know what happened; don't know how to further investigate this. >>Has somebody else similar experiences? Is stability going down for >>Stable kernel? > > > Could you take a look at the instructions in the Handbook on setting up > for kernel debugging, compile the kernel with DDB, and generate stack > traces for the hung processes + the output of "show lockedvnodes"? Also, > if you can get a core dump, it might be interesting to see the output of > netstat -mb on the core. Finally, are you using any features like NIS or > NFS? Having umount stuck in sbwait sounds like a fairly unusual failure > mode unless you're using NFS. Thanks. Indeed, stability of Stable is still OK. For 1) above, that happened on an NFS server. So you could have a point here, though the 'overloaded' filesystem was not NFS-mounted, but local. Is NFS known to cause problems of this kind? For 2), there seem to be a problem with USB, if there's a VIA chipset on the motherboard. I have received one more confirmation of the same problem with the same hardware. No other response on this issue from the list though. Regards, Rob.