Date: Fri, 2 Mar 2007 10:49:00 -0500 From: Mike Meyer <mwm@mired.org> To: "Steven Hartland" <killing@multiplay.co.uk> Cc: freebsd-hackers@freebsd.org, Jeremy Chadwick <koitsu@FreeBSD.org>, freebsd-stable@freebsd.org, Eric Anderson <anderson@freebsd.org> Subject: Re: sysinstall creates corrupt filesystems after repartitioning Message-ID: <17896.18284.528644.992894@bhuda.mired.org> In-Reply-To: <00eb01c75ce0$b0430380$b3db87d4@multiplay.co.uk> References: <00cb01c75c5b$4205e390$b3db87d4@multiplay.co.uk> <45E82660.4030107@freebsd.org> <008101c75cd1$42a4df10$b3db87d4@multiplay.co.uk> <45E830A8.8020104@freebsd.org> <20070302144409.GA4431@icarus.home.lan> <00eb01c75ce0$b0430380$b3db87d4@multiplay.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
In <00eb01c75ce0$b0430380$b3db87d4@multiplay.co.uk>, Steven Hartland <killing@multiplay.co.uk> typed: > 2. Once the blank /usr was mounted over the working nfs /usr > apps under /usr couldnt be run e.g. vim gave me no such file.. This is correct behavior. If you want to see the files underneath a mounted file system, you need to use the union option on the mount. sysinstall doesn't expect you to have live file systems mounted, so doesn't do that. > After unmounting the ufs /usr using "umount -f /dev/da0s1f", > without -f it gave a error due to use even know nothing was > in use on it, the functionaility returned. Are you positive nothing was in use on it? In particular, could sysinstall have opened something on it? In any case, unmounting the file system causeing that functionality to return is expected. <mike -- Mike Meyer <mwm@mired.org> http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?17896.18284.528644.992894>