this post was submitted on 09 Oct 2024
10 points (91.7% liked)

Linux

7936 readers
6 users here now

Welcome to c/linux!

Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!

Rules:

  1. Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.

  2. Be respectful: Treat fellow community members with respect and courtesy.

  3. Quality over quantity: Share informative and thought-provoking content.

  4. No spam or self-promotion: Avoid excessive self-promotion or spamming.

  5. No NSFW adult content

  6. Follow general lemmy guidelines.

founded 1 year ago
MODERATORS
 

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 shady@192.168.50.16:/home/shady/skynet /home/skynet
shady@192.168.50.16'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$
you are viewing a single comment's thread
view the rest of the comments
[–] jesta@lemmy.world 5 points 1 week ago (2 children)

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

[–] Dust0741@lemmy.world 1 points 1 week ago (1 children)

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

[–] jesta@lemmy.world 5 points 1 week ago* (last edited 1 week 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.

[–] Dust0741@lemmy.world 1 points 1 week ago (1 children)
skynet@skynet:/home$ fusermount -u /home/skynet
fusermount: entry for /home/skynet not found in /etc/mtab
[–] jesta@lemmy.world 1 points 1 week ago (1 children)

can you see the the mount using mount ?

[–] Dust0741@lemmy.world 2 points 1 week ago (1 children)

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@lemmy.world 2 points 1 week ago (1 children)

umount /home/skynet

should release it.

[–] Dust0741@lemmy.world 1 points 1 week ago (1 children)

umount: /home/skynet: target is busy.

[–] jesta@lemmy.world 4 points 1 week ago (2 children)

umount -f /home/skynet

You can force it.

[–] Dust0741@lemmy.world 1 points 1 week ago (1 children)

uh....didn't work

skynet@skynet:~$ sudo umount -f /home/skynet
umount: /home/skynet: target is busy.
[–] jesta@lemmy.world 3 points 1 week ago* (last edited 1 week ago) (1 children)

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

[–] Dust0741@lemmy.world 2 points 1 week ago (1 children)

i have docker containers using that folder. could that be it?

[–] jesta@lemmy.world 4 points 1 week ago (1 children)
[–] Dust0741@lemmy.world 4 points 1 week ago

thank you so much. everything is back.

[–] Dust0741@lemmy.world 1 points 1 week ago

should I use -fl