From owner-freebsd-questions@FreeBSD.ORG Fri Jan 4 19:47:03 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 11A0916A418; Fri, 4 Jan 2008 19:47:03 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 276CE13C45D; Fri, 4 Jan 2008 19:47:01 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <477E8D35.4060309@FreeBSD.org> Date: Fri, 04 Jan 2008 20:47:01 +0100 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031) MIME-Version: 1.0 To: Hugo Silva References: <477E5BB9.6090104@barafranca.com> In-Reply-To: <477E5BB9.6090104@barafranca.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: pjd@freebsd.org, freebsd-questions@freebsd.org Subject: Re: ggatec hanging on 7.0-RC1/amd64 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jan 2008 19:47:03 -0000 Hugo Silva wrote: > Hi, > > I'm experiencing some problems while attempting to export a ZVOL with > ggated on a gigabit network. > > > All servers are running FreeBSD 7.0-RC1 on amd64, and using bce NICs. > > > > client# ggatec create -t 6 -u 0 172.16.100.200 /dev/zvol/storage/vol0 > > client# ls -l /dev/ggate* > crw-r----- 1 root operator 0, 115 Jan 4 06:23 /dev/ggate0 > > client# newfs /dev/ggate0 > load: 0.00 cmd: newfs 51187 [g_waitidle] 0.00u 0.00s 0% 792k > ^C^C^C^C^C^C^C^C^C^C^C^C^C^C > > > The same happens with a file exported on a UFS filesystem (so it's not a > ZFS problem): > > > client# ggatec create -u100 172.16.100.200 /usr/lol > > client# dir /dev/ggate100 > crw-r----- 1 root operator - 0, 115 Jan 4 06:23 /dev/ggate100 > > client# newfs /dev/ggate100 > load: 0.00 cmd: newfs 52306 [g_waitidle] 0.00u 0.00s 0% 792k > load: 0.00 cmd: newfs 52306 [g_waitidle] 0.00u 0.00s 0% 792k > load: 0.00 cmd: newfs 52306 [g_waitidle] 0.00u 0.00s 0% 792k > ^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^Z^Z^Z^Z^Z^Z^Z^Z^Z^Z^Z^Z^Z^Z^Z^Z^Z^Z^Z^Z > > > > After several killall -9 ggatec and ggatec -fuX (-uX will stop working > after awhile with "device busy", even though no ggatec process is using > it anymore and the newfs process is also killed), the following happens: > > # killall -9 ggatec > load: 0.00 cmd: killall 52400 [sysctl lock] 0.00u 0.00s 0% 244k > load: 0.00 cmd: killall 52400 [sysctl lock] 0.00u 0.00s 0% 244k > load: 0.00 cmd: killall 52400 [sysctl lock] 0.00u 0.00s 0% 244k > > At this point, the machine is dead. It still replies to pings, but > processes are definitely unkillable now and even trying to login via SSH > doesn't work: > > $ ssh client > load: 0.05 cmd: ssh 2127 [sbwait] 0.00u 0.00s 0% 3180k > [hangs forever] > > > /etc/gg.exports on the server: > client.ip/32 RW /dev/zvol/storage/vol0 > > > Am I missing something terribly obvious ? I have done this many times > before and never encountered this problem.. Please see http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html for how to proceed. Kris