Date: Fri, 2 Mar 2007 06:44:09 -0800 From: Jeremy Chadwick <koitsu@FreeBSD.org> To: Eric Anderson <anderson@freebsd.org> Cc: freebsd-hackers@freebsd.org, Steven Hartland <killing@multiplay.co.uk>, freebsd-stable@freebsd.org Subject: Re: sysinstall creates corrupt filesystems after repartitioning Message-ID: <20070302144409.GA4431@icarus.home.lan> In-Reply-To: <45E830A8.8020104@freebsd.org> References: <00cb01c75c5b$4205e390$b3db87d4@multiplay.co.uk> <45E82660.4030107@freebsd.org> <008101c75cd1$42a4df10$b3db87d4@multiplay.co.uk> <45E830A8.8020104@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Mar 02, 2007 at 08:11:52AM -0600, Eric Anderson wrote: > Mounting an NFS share on top of a skimmed down /usr is very common, and > very desirable. You may mount /usr from a small read-only partition > (vnode file, etc) and then mount a different partition or NFS over it if > you detect the one you want. > > I think this comes down to: if it hurts, stop doing it. :) > > Maybe sysinstall should warn you that you are double mounting, but I > don't want it to stop letting me do it. Are we absolutely sure overlaying NFS + local UFS filesystems like this is the cause of the filesystem corruption? If Eric's doing it and it's working fine, I'm left wondering if there's maybe sysinstall isn't handling something right. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070302144409.GA4431>