On Thu 03 Mar 2016 at 23:17:19 (-0500), Cindy-Sue Causey wrote: > On 3/3/16, Andrew McGlashan <andrew.mcglas...@affinityvision.com.au> wrote: > > > > On 4/03/2016 3:07 AM, Adam Wilson wrote: > >> On Fri, 4 Mar 2016 03:03:53 +1100 Andrew McGlashan > >> <andrew.mcglas...@affinityvision.com.au> wrote: > >>> It also may have been files in the file system, but where another file > >>> system mount hides them.... > >> > >> What does this mean? Mounts overlapping and hiding other mounts? > >> > >> Explain, please. > > > > Yes, this is more likely to happen to the root file system. > > > > Say you have a bunch of files in /boot, but for some reason you have a > > /boot partition that wasn't mounted when those files were created .... > > then you mount the /normal/ boot partition over it and now the other > > files are now hidden from view, but still taking up space. > > > Is that behavior as designed and thus expected, or is it a glitch?
It is as defined by mount's man page. > My brain's thinking it should either complain and refuse to continue > else obliterate and replace. Typically a mount point is an empty directory. However, this does not _have to be_ the case. > To me it would be... safer that it halt and complain rather than > destroy, but all that shows is that I most likely just don't > understand the function. Nothing is destroyed, but just inaccessible or "hidden". > Do (and/or should) the original files "reappear" later? As soon as you unmount the device that you mounted on that directory. Cheers, David.
