Warn a user prior to making data inaccessible via mount
|Reported by:||jgreco||Owned by:|
Pretty sure at this point that's what happened to this guy
If a proposed mountpoint doesn't exist, go ahead and use it.
If it exists but is empty, that's probably fine too, but there may be edge cases.
If it exists and isn't empty, I suggest that this is a problem that should not be silently ignored. My preferred solution would probably be to refuse to create the mountpoint at all.