sysinstall creates corrupt filesystems after repartitioning

[Mike Meyer]

In <00eb01c75ce0$b0430380$b3db87d4 at multiplay.co.uk>, Steven Hartland <killing at 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 at mired.org>		http://www.mired.org/consulting.html
Independent Network/Unix/Perforce consultant, email for more information.