From owner-freebsd-stable@FreeBSD.ORG Fri Nov 12 14:27:05 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6DDA9106566B; Fri, 12 Nov 2010 14:27:05 +0000 (UTC) (envelope-from avg@freebsd.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 562148FC18; Fri, 12 Nov 2010 14:27:03 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id QAA00315; Fri, 12 Nov 2010 16:27:01 +0200 (EET) (envelope-from avg@freebsd.org) Message-ID: <4CDD4EB4.40004@freebsd.org> Date: Fri, 12 Nov 2010 16:27:00 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.12) Gecko/20101029 Lightning/1.0b2 Thunderbird/3.1.6 MIME-Version: 1.0 To: Alexander Zagrebin References: <4CDD2F5F.2000902@freebsd.org> In-Reply-To: X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org, freebsd-stable@freebsd.org, Martin Matuska Subject: Re: 8.1-STABLE: problem with unmounting ZFS snapshots X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Nov 2010 14:27:05 -0000 on 12/11/2010 16:00 Alexander Zagrebin said the following: > Thanks for your reply! > >>> 2. the umount is waiting for disk >>> #ps | egrep 'PID|umount' >>> PID TT STAT TIME COMMAND >>> 958 0 D+ 0:00,04 umount /mnt >>> # procstat -t 958 >>> PID TID COMM TDNAME CPU PRI >> STATE WCHAN >>> 958 100731 umount - 3 133 >> sleep mntref >> >> procstat -kk > > $ ps a | grep umount > 86874 2- D 0:00,06 umount /mnt > 90433 3 S+ 0:00,01 grep umount > > $ sudo procstat -kk 86874 > PID TID COMM TDNAME KSTACK > 86874 100731 umount - mi_switch+0x176 > sleepq_wait+0x42 _sleep+0x317 vfs_mount_destroy+0x5a dounmount+0x4d4 > unmount+0x38b syscall+0x1cf Xfast_syscall+0xe2 > Looks like possible mnt_ref leak. I think that something like that was fixed some not long time ago. Perhaps you either don't have the fix or there is another leak. What revision do you have? Perhaps Martin has an insight here. -- Andriy Gapon