I may have messed things up… I had a lot of docker config and data stored in /home/skynet I then ran a sshfs command and it disappeared. I was trying to send the contents of /home/skynet (server) to /home/shady/skynet (desktop). This was in order to be able to edit the files on the server on the desktop via VSCodium.

I’d love recommendations on how to do this, but first how do I get my files back???

Here is what I did

skynet@skynet:~/docker/keycloak$ sudo sshfs -o allow_other,default_permissions [email protected]:/home/shady/skynet /home/skynet
[email protected]'s password: 
skynet@skynet:~/docker/keycloak$ cd
skynet@skynet:~$ ks
-bash: ks: command not found
skynet@skynet:~$ ls
skynet@skynet:~$ ls -a
.  ..
skynet@skynet:~$ lsblk
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda           8:0    0   3.6T  0 disk 
├─sda1        8:1    0    16M  0 part 
└─sda2        8:2    0   3.6T  0 part /media/devmon
nvme0n1     259:0    0 476.9G  0 disk 
├─nvme0n1p1 259:1    0   476G  0 part /
├─nvme0n1p2 259:2    0     1K  0 part 
└─nvme0n1p5 259:3    0   975M  0 part [SWAP]
skynet@skynet:~$ cd /home
skynet@skynet:/home$ ls
changedetection  linuxbrew  skynet  syncthing
skynet@skynet:/home$ cd skynet/
skynet@skynet:~$ ls
skynet@skynet:~$ ls -a
.  ..
skynet@skynet:~$ cd /home
skynet@skynet:/home$ ls
changedetection  linuxbrew  skynet  syncthing
skynet@skynet:/home$ fusermount -u /home/shady/skynet
fusermount: bad mount point /home/shady/skynet: No such file or directory
skynet@skynet:/home$ sudo journalctl -u sshfs
-- No entries --
skynet@skynet:/home$
  • @jesta
    link
    English
    57 days ago

    sudo sshfs -o allow_other,default_permissions shady@192.168.50.16:/home/shady/skynet /home/skynet

    You mounted your desktop files on top of the server files.

    fusermount -u /home/shady/skynet

    this should be

    fusermount -u /home/skynet

    • @Dust0741OP
      link
      English
      17 days ago

      some sources online say that rebooting will revert it…do I risk it?

      • @jesta
        link
        English
        5
        edit-2
        7 days ago

        if rebooting is and option, it will release the mounts. And should be safe because mounting on top of an existing path doesn’t really break anything. the original files still exist, but are just hidden because they are under the new mount. Once the mount is released, everything should be as it was.

    • @Dust0741OP
      link
      English
      17 days ago
      skynet@skynet:/home$ fusermount -u /home/skynet
      fusermount: entry for /home/skynet not found in /etc/mtab
      
      • @jesta
        link
        English
        17 days ago

        can you see the the mount using mount ?

        • @Dust0741OP
          link
          English
          27 days ago

          running mount prints a lot, but at the bottom it has: shady@192.168.50.16:/home/shady/skynet on /home/skynet type fuse.sshfs (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other)

          • @jesta
            link
            English
            27 days ago

            umount /home/skynet

            should release it.

            • @Dust0741OP
              link
              English
              17 days ago

              umount: /home/skynet: target is busy.

              • @jesta
                link
                English
                47 days ago

                umount -f /home/skynet

                You can force it.

                • @Dust0741OP
                  link
                  English
                  17 days ago

                  should I use -fl

                • @Dust0741OP
                  link
                  English
                  17 days ago

                  uh…didn’t work

                  skynet@skynet:~$ sudo umount -f /home/skynet
                  umount: /home/skynet: target is busy.
                  
                  • @jesta
                    link
                    English
                    3
                    edit-2
                    7 days ago

                    you most likely have a terminal open that is currently in that path.