From owner-freebsd-current@FreeBSD.ORG Fri Feb 3 18:50:56 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E66A0106568D for ; Fri, 3 Feb 2012 18:50:56 +0000 (UTC) (envelope-from dlt@mebtel.net) Received: from mail941c35.nsolutionszone.com (mail941c35.nsolutionszone.com [209.235.152.131]) by mx1.freebsd.org (Postfix) with ESMTP id 920868FC0C for ; Fri, 3 Feb 2012 18:50:56 +0000 (UTC) X-POP-User: dlt.mebtel.net Received: from localhost (99-194-23-158.dyn.centurytel.net [99.194.23.158]) by mail941c35.nsolutionszone.com (8.13.6/8.13.1) with ESMTP id q13IoruQ005300; Fri, 3 Feb 2012 18:50:54 GMT Date: Fri, 3 Feb 2012 13:50:53 -0500 From: Derek Tattersall To: Ryan Stone Message-ID: <20120203185053.GA11019@oriental.arm.org> References: <20120203143438.GA2798@oriental.arm.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-CSC: 0 X-CHA: v=1.1 cv=9TUB+RS35G5y5DT6KTRCAKUVG+9gOaz+XaEOQ/3CU8k= c=1 sm=1 a=wom5GMh1gUkA:10 a=AOmNu5pVU98A:10 a=P2oOn6vrs4wA:10 a=GPr01A5e9VcA:10 a=8nJEP1OIZ-IA:10 a=5FSmvsqyZ8dLHOg+TByL6Q==:17 a=pGLkceISAAAA:8 a=xwPayol1AAAA:8 a=CjxXgO3LAAAA:8 a=ZrG5GFV56G0ZXiGiZ0gA:9 a=wPNLvfGTeEIA:10 a=MSl-tDqOz04A:10 a=0Ob1RWNGeVAA:10 a=rC2wZJ5BpNYA:10 a=5FSmvsqyZ8dLHOg+TByL6Q==:117 Cc: current@freebsd.org Subject: Re: Can't umount a formerly mounted drive X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dlt@mebtel.net List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Feb 2012 18:50:57 -0000 * Ryan Stone [120203 13:41]: > On Fri, Feb 3, 2012 at 9:34 AM, Derek Tattersall wrote: > > I have two drives in a x86-64 machine.  Drive ada2 has current on it, and > > drive ada1 has 9-stable on it.  At some point, while running current, I > > mounted the /home partition from stable to copy some files and re-ipled > > the system into stable.  every thing worked properly.  Some time later I > > ipled current again.  I then noticed that the stable /home was mounted > > on /mnt.  I tried to umount it but the operation failed as /dev/ada1p7 > > was not considered mounted.  Yet with out mounting I could access all > > the files on stable's /home, I could create and delete files. > > > > The current system was cvsup'ed on Wednesday this week, while the stable > > system was cvsup'ed last Sunday.  Neither system has exhibited any > > hiccups.  Can somebody explain what has happened her on the current > > system and how it should be corrected? > > Does "mount" list anything as being mounted on /mnt? If not, are you > sure that /mnt isn't a symlink to somewhere else? Or maybe the > contents of the home directory were copied to /mnt by accident? mount command on the current system does not list anything under /mnt. ls /mnt on the current system list the top level directories on ada1p7, the stable /home. It lists them as soon as a user logs in on a newly booted current system. It's really frustrating. -- Best regards, Derek Tattersall dlt@mebtel.net dlt666@yahoo.com dtatters@gmail.com