From owner-freebsd-fs@FreeBSD.ORG Thu Dec 20 02:29:29 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9EADA1D7 for ; Thu, 20 Dec 2012 02:29:29 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-oa0-f54.google.com (mail-oa0-f54.google.com [209.85.219.54]) by mx1.freebsd.org (Postfix) with ESMTP id 5C6028FC0C for ; Thu, 20 Dec 2012 02:29:29 +0000 (UTC) Received: by mail-oa0-f54.google.com with SMTP id n9so2847223oag.27 for ; Wed, 19 Dec 2012 18:29:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=D9H7y52irUVZtagW7qyCKeIZ/re2Us2fTnxLn7hoigo=; b=dppe6oekJCQm4L5IV9YuN43xksZ/7TCTCm5+fXCOm0ObdKr0giqb/vWKp34OS+r4Fh IgqdpmSCALu8VMGXKbKP3iSQlFSr7T/xQFVCN7DOHDIgVLb8Fs/sR5XN1/IVUCieeS9b BY5vjsPLnRzHWiUC9XQPCTKu3cuSkdSsZ9QPd5xATjUUubBvkJdobJ8gs5peheEm/JOT I1RjEnFog+BgqvarjOE/rgsw0nh+wKuxhymnZkKDui9ont13bRTi1jyiOYgQYPNsf++r eCD2KI8wo/BUdaftF9n9Z4CZKaqjtNctbJC/Ecf9ewwJSuVENoaDvrt95xuvdj1OLIGB qYtQ== MIME-Version: 1.0 Received: by 10.182.95.205 with SMTP id dm13mr6833137obb.9.1355970563560; Wed, 19 Dec 2012 18:29:23 -0800 (PST) Received: by 10.76.143.33 with HTTP; Wed, 19 Dec 2012 18:29:23 -0800 (PST) In-Reply-To: References: Date: Wed, 19 Dec 2012 18:29:23 -0800 Message-ID: Subject: Re: umount -f broken again [with devfs/NFS] From: Garrett Cooper To: FreeBSD FS Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Dec 2012 02:29:29 -0000 On Wed, Dec 19, 2012 at 6:23 PM, Garrett Cooper wrote: > Ran into this with a build of CURRENT 2 week or so old version of > CURRENT (gjb's livecd) and while unmounting devfs with a week old > build: > > # umount -f /ifs > umount: unmount of /ifs failed: Device busy > # uname -a > FreeBSD wf158.west.isilon.com 10.0-CURRENT FreeBSD 10.0-CURRENT #3 > r+5a05236: Wed Dec 12 17:35:14 PST 2012 > root@wf158.west.isilon.com:/usr/obj/usr/src/sys/ISI-GENERIC amd64 > > My gut reaction is that some recently changes to VFS probably > broke this (a couple week old 9-STABLE build just hangs on an NFS > mountpoint that's gone out to lunch). Interesting. Killed a "rogue mergemaster" instance and I noticed that the umount -f command I had going on the 9-STABLE box is still hung in newnfs state BUT the mountpoint is gone: load: 0.11 cmd: umount 91115 [newnfs] 521.60r 0.00u 0.09s 0% 1440k load: 0.11 cmd: umount 91115 [newnfs] 521.64r 0.00u 0.09s 0% 1440k load: 0.11 cmd: umount 91115 [newnfs] 521.68r 0.00u 0.09s 0% 1440k load: 0.11 cmd: umount 91115 [newnfs] 521.72r 0.00u 0.09s 0% 1440k $ mount | grep /mnt/temp || echo "not found" not found $ ps auxww | grep umount | grep -v grep root 91114 0.0 0.0 40152 2512 11 I+ 6:15PM 0:00.03 sudo umount -f /mnt/temp root 91115 0.0 0.0 9872 1456 11 D+ 6:15PM 0:00.10 umount -f /mnt/temp $ uname -a FreeBSD forza.west.isilon.com 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #0 r+2fd0a57: Mon Dec 3 12:02:18 PST 2012 gcooper@forza.west.isilon.com:/usr/obj/usr/src/sys/FORZA amd64 I'm going to restart the box in a minute (have to swap out some hardware), but I thought this was kind of strange. Thanks, -Garrett