Re: mount existing tmpfs mounts a new tmpfs

[Phil Susi <psusi@ubuntu.com>]

On 6/22/2015 4:20 AM, Karel Zak wrote:
> On Sun, Jun 21, 2015 at 10:00:51PM -0400, Phillip Susi wrote:
>> Forwarding this from debian bug #772419: Run mount /run, and it mounts
>> a new tmpfs over top of the existing one in /run ( even if /run isn't
>> listed in /etc/fstab ), hiding the existing files.  It should say that
>> it is already mounted.
>
> We usually don't play any policy games in userspace (exception is
> mount -a).  If it's supported by kernel then it's correct behaviour.
> And IMHO it's really correct behaviour because it creates a *new*
> filesystem.

The single argument form of mount isn't *supposed* to create a new 
filesystem.  It is supposed to mount one described by /etc/fstab if it 
is not already mounted.  It should not be looking up /proc/mounts and 
treating what it finds there as if it was an /etc/fstab entry, and then 
blindly trying to remount the already mounted filesystem.  Only the two 
argument form of mount should do this.

--
To unsubscribe from this list: send the line "unsubscribe util-linux" in