Date: Fri, 2 Mar 2007 13:46:55 -0000 From: "Steven Hartland" <killing@multiplay.co.uk> To: "Eric Anderson" <anderson@freebsd.org> Cc: freebsd-hackers@freebsd.org, freebsd-stable@freebsd.org Subject: Re: sysinstall creates corrupt filesystems after repartitioning Message-ID: <008101c75cd1$42a4df10$b3db87d4@multiplay.co.uk> References: <00cb01c75c5b$4205e390$b3db87d4@multiplay.co.uk> <45E82660.4030107@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Eric Anderson wrote:
> I don't know about the fs corruption, but the double mounts is
> something you asked it to do (maybe unknowingly). When you added
> that partition, one of the options is to mount it.
Clearly an easy work around in that case then but personally
I would expect a mount to a directory already in use by another
mount point to fail. Taking even further a mount to a directory
that is not actually empty should fail. IIRC this is how solaris
behaves but its been a while.
Checking for an empty target directory certainly makes sence to
me is there some case where it would be desirable to allow this
to happen? If so maybe a force flag should created without which
a mount to a none empty dir would fail. Either way allowing
multiple mounts to the same location is bound to cause all manor
of confusion and should be prevented.
Steve
================================================
This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it.
In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337
or return the E.mail to postmaster@multiplay.co.uk.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?008101c75cd1$42a4df10$b3db87d4>