Re: mount weirdness

[Dennis Wicks <wix@mgssub.com>]

David Wright wrote on 8/8/19 9:04 AM:
> On Thu 08 Aug 2019 at 08:19:22 (-0000), Curt wrote:
> > On 2019-08-05, Dennis Wicks <wix@mgssub.com> wrote:
> > > So anyway, I typed in "sudo mount /dev/sdb2 /wa1" and it
> > > seemed to finish successfully, but "ls /wa1" indicated that
> > > in fact it had not. Nothing mounted on wa1! Many other tests
> > > told me the same thing. "umount /wa1" said "not mounted"!
> >
> > Would this be the result if /dev/sdb2 were already mounted (i.e. nothing?).
>
> Try it. I, at least, would be interested in the result.
> So far, the voting is 2-1 against seeing what I see:
>
> wren 08:50:11 ~# lsblk -f | grep sda7
> ├─sda7       ext4        swan07      4a4e352f-2180-4083-92b4-f46e4e0104b4 /wrenbk
> wren 08:50:26 ~# mkdir /wa1 /somethingelse
> wren 08:50:49 ~# mount /dev/sda7 /somethingelse
> mount: /dev/sda7 is already mounted or /somethingelse busy
>         /dev/sda7 is already mounted on /wrenbk
> 32 wren 08:51:16 ~# mount /dev/sda7 /wa1
> mount: /dev/sda7 is already mounted or /wa1 busy
>         /dev/sda7 is already mounted on /wrenbk
> 32 wren 08:51:31 ~# rmdir /wa1 /somethingelse
> wren 08:51:53 ~#
>
> By way of explanation, the prompt is
> export PROMPT_COMMAND='MYPROMPT="$? " && [ "$MYPROMPT" = "0 " ] && MYPROMPT=""'
> export PS1='\[\e[1;33;41m\]$MYPROMPT\[\e[1;37;44m\]\H \t \w\[\e[0m\]\$ ' # blue
> but I normally cut it to reduce clutter.
>
> > Many other tests. What about 'mount' from an xterm to see what's mounted
> > and what ain't and where?
> >
> > Did you show your /etc/fstab file (cut and paste)? If so, I must've missed
> > it.
> >
> > BTW, what's with the exclamation points? Makes you seem enthusiastic.
>
> Yes, I couldn't figure that out, nor what good a note in /etc/fstab
> would do (in the reply to Thomas). Does one peruse that file each time
> one reboots?
>
> Cheers,
> David.
Greetings;

What system are you running, David? I am running vanilla 
Debian bullseye, recently upgraded. Been running Debian for 
years and have never gotten those errors. This is what 
happens to me.

 wix@dgwicks:~$ s mount /dev/sdc1 /test1
 wix@dgwicks:~$ s mount /dev/sdc1 /test2
 wix@dgwicks:~$ findmnt /dev/sdc1
 TARGET SOURCE    FSTYPE OPTIONS
 /test1 /dev/sdc1 xfs    rw,relatime,attr2,inode64,noquota
 /test2 /dev/sdc1 xfs    rw,relatime,attr2,inode64,noquota
 wix@dgwicks:~$
 wix@dgwicks:~$ s mount -v /dev/sdc1 /work-1
 mount: /dev/sdc1 mounted on /work-1.
 wix@dgwicks:~$ findmnt /dev/sdc1
 TARGET  SOURCE    FSTYPE OPTIONS
 /test1  /dev/sdc1 xfs    rw,relatime,attr2,inode64,noquota
 /test2  /dev/sdc1 xfs    rw,relatime,attr2,inode64,noquota
 /work-1 /dev/sdc1 xfs    rw,relatime,attr2,inode64,noquota
 wix@dgwicks:~$

Do you have some environment variable set or something in an 
ini or rc file that makes mount behave in a more strict way 
than standard?

No, I don't look at fstab every time I reboot. Just when I 
get things like failed mounts. In which case seeing that 
note will remind me what to look at/for.

Regards,
Dennis