From owner-freebsd-fs@FreeBSD.ORG Thu Apr 28 05:19:17 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 42FD7106564A for ; Thu, 28 Apr 2011 05:19:17 +0000 (UTC) (envelope-from grarpamp@gmail.com) Received: from mail-pv0-f182.google.com (mail-pv0-f182.google.com [74.125.83.182]) by mx1.freebsd.org (Postfix) with ESMTP id A261C8FC12 for ; Thu, 28 Apr 2011 05:19:16 +0000 (UTC) Received: by pvg11 with SMTP id 11so2136618pvg.13 for ; Wed, 27 Apr 2011 22:19:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=5h+Hn3TiulWMRm2D547M//NslGLDLOGV2m0LJ+386bg=; b=xHH4VgqOaN8aJp/4mo97bLA+0Zxnx/FJ5tfthZ4vm6+rilPJosGfT9IKDYpGX4a62A wTfs5AHS5lpmvNQznKbODT3R804YrqWMzfAnQxWF5mmzWnu6fSu72pCTkJXxiMt2BX5I +tgB4Yrw/TpMmQugkwALA1EMmlDvVXTQF5ntQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=PDkb68t31NZvDQmlg/+b3yaWIO7wcxXxS7uqrQQj53lFyfkyfrm4GffhpSmAsUjLLF Bib3RanbUEJPc/lX62KSYeQ3v0Tqt6I/g1KQaC0sOHjhSU94qK6WMcRES9EWgTWPqXUJ AJmlB3aRujIz5Q6gAL3o2/JAZSomCkzg3Ci6s= MIME-Version: 1.0 Received: by 10.142.218.15 with SMTP id q15mr995020wfg.311.1303966165285; Wed, 27 Apr 2011 21:49:25 -0700 (PDT) Received: by 10.142.177.20 with HTTP; Wed, 27 Apr 2011 21:49:25 -0700 (PDT) Date: Thu, 28 Apr 2011 00:49:25 -0400 Message-ID: From: grarpamp To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=UTF-8 Subject: Softupdates and umount, bug, fixed? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Apr 2011 05:19:17 -0000 At one point in the not too distant past you could... - newfs -U and mount two disks - fill one fs with a reasonable hierarchy of a million inodes - rsync that over to the second fs - wait till df -i had the same inode count - blow away some number of inodes from the first, say 5000 - immediately after the rm ; umount the second fs That would leave you with a difference in df -i count. And a filesystem that needed fsck -fy umount didn't seem wait for, or sync, the fs. Has this been fixed yet?