From: robin_listas@es.invalid   
      
   On 2023-04-01 01:46, bad sector wrote:   
   > On 3/31/23 16:27, Carlos E.R. wrote:   
   >> On 2023-03-31 21:03, bad sector wrote:   
   >>> On 3/31/23 07:41, Carlos E.R. wrote:   
   >>>> lsblk --output   
   >>>> NAME,KNAME,RA,RM,RO,PARTFLAGS,SIZE,TYPE,FSTYPE,LABEL,PARTLA   
   EL,PTTYPE,MOUNTPOINT,UUID,PARTUUID,WWN,MODEL,ALIGNMENT | less -S   
   >>>   
   >>> Cool, but it doesn't answer two of my questions :-)   
   >>>   
   >>> 1   
   >>> In the attempted command "mount  /dev/sda4 /0/sa04" the   
   >>> 'mountpoint' was /0/sa04. The error message stating that   
   >>> THE mountpoint was in use is BS needing to be both clarified   
   >>> AND fixed.   
   >>   
   >> I pose that pretense is just an error in the blob that sits between   
   >> the chair and the computer :-P  :-D   
   >>   
   >> If the message says the mount point is in use, then it is. Actually,   
   >> the message said two things with and 'or' in between.   
   >>   
   >>   
   >> You can use the command "mount" to see what is actually mounted and   
   >> where. And "lsof" to see what is busy.   
   >>   
   >>   
   >>>   
   >>> 2   
   >>> How do I mount the prinmary (or only) disk partition-4   
   >>> under /0/sa04?   
   >>   
   >> You have to find first where is the error.   
   >>   
   >   
   > The first error I see is in the error message i.e. I can mount a device   
   > under many mountpoints   
   >   
   > # mount PARTUUID=04edd347-8460-c449-a350-4716a10d0386  /0/sa04   
   > # mount PARTUUID=04edd347-8460-c449-a350-4716a10d0386  /0/sb04   
   > # mount PARTUUID=04edd347-8460-c449-a350-4716a10d0386  /0/sc04   
   >   
   > never reports "already mounted", there may well be a limit of how many   
   > mountpoints I can use but that's above my paygrade.   
   >   
   > # umount /0/sc04   
   >   
   > leaves only the first 2 mountpoints mounted under   
   >   
   > # umount PARTUUID=04edd347-8460-c449-a350-4716a10d0386   
   >   
   > unmounts it from the next to last remaining mountpoint   
   >   
   > and so on until there are no more.   
   >   
   >   
   > So in response to   
   >   
   > mount /dev/sda4 /0/sa04   
   >   
   > the message "already mounted OR mount point busy" can only mean that the   
   > mountpoint (/0/sa04) is busy i.e. some device is already mounted under   
   > /0/sa04. But /0/sa04 is *my* mountpoint, the system doesn't know it   
   > exists so   
      
   Of course it knows it exists.   
      
   >   
   > 1   
   > how can it mount anything under it?   
   >   
   > 2   
   > how does it get the authority to mount ANY partition without being   
   > 'commanded' by root to mount it either in fstab or explicitly?   
      
   There are several services and applications that can effect mounts.   
      
   >   
   > lsof doesn't tell me anything significant   
   >   
   > and your lsblok one-liner (thanks BTW) just ends with   
   >   
   > "[14551.227219] /dev/sda4: Can't open blockdev"   
      
   Is it really a blockdev? Do check it.   
      
   ls -l /dev/sda*   
      
   >   
   > Maybe THAT's the problem, "the criminal is using dev-names!!!!"   
   >   
   > Well, I'nm NOT going to start copy-pasting two-yard long UUIDS just   
   > becasue the NSA wanted absolute traceability on everything including La   
   > Plume de Ma Tante.   
      
   LOL! The NSA? Really?   
      
   > As an extreme worst case scenario (should I ever end   
   > up with my back to the wall) I might either label partitions with the   
   > last VERY-FEW digits of the disk RealHardware model number and partition   
   > number, or I might just boot Slackware and do 'mount /dev/sda4 /0/sa04'.   
   >   
   >   
      
   --   
   Cheers, Carlos.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)