is there a way to recover snapshots to a share that has been completely deleted?
I tried moving my docker install over to my new ssd volume and used scp to move the @docker folder to the new volume so I wouldn’t lose all my containers. I started getting permissions errors, but it seemed I had fixed them by starting the containers with pgid/puid as root, then changing back to the dockerlimited user and starting the containers again. seemed to work fine but then watchtower updated an image and it totally fried that container, with some btrfs can’t remove subvolume issue. i couldn’t delete, reset or start the container so it was like frozen. i tried to create a brand new container of the same image using portainer and it failed with another ocr init not found error. so i tried a nuclear option of chmod 777 of the entire @docker folder and i still wasn’t able to create a container with portainer. it was giving the same error. so I figured the permissions and everything were so screwed up, the only thing to do is start from fresh. I used a docker-autocompose script to make compose files of all my containers and saved them in my docker shared folder.
Then i uninstalled container manager and checked the box to delete images, containers and shares. this deleted my docker share and the docker share i created as a backup. I think everything must still be there because even there’s no share folders attributed to that volume, storage manager says theres still data on the drive. when i view usage details I see that snapshot is taking what i would expect to the correct amount for a full backup of the share folder i’d had but i can’t tell for sure. Still I’m fairly positive the snapshot is my of my docker share. snapshot logs have this line from 5am today: ‘Took a shared folder snapshot [GMT-05-2023.07.24-05.00.01] from share [docker] by [scheduler].’
How can I recover the share from the snapshot when the share doesn’t exist anymore? If I create a new shared folder with the same name, would I be able to use the snapshot then? I’m honestly afraid to touch anything now because it seems at every step I just keep shooting myself in the foot and making things worse. Idk what to do.
Yes I can SSH in. I think the snapshot exists but is not mounted as a btrfs subvolume. In storage manager, it gives an overview of what’s taking up space on your volume, and snapshots shows it taking up space so I’m certain it’s there. the subvolume list on my other volume is showing the other snapshots I’ve created for other shared folders though.
from the research I did, the @docker folder at the volume root holds all the volumes, images, subvolumes, etc. and I did copy that over.
Do you happen to know if I find the snapshot folder and download it, will there be anything recoverable? Or would it just be like, hashes and unintelligble stuff?
I think the snapshot exists but is not mounted as a btrfs subvolume.
Is it not listed when you try running btrfs subvolume list .? You might need to change the . to a path that is on the array.
from the research I did, the @docker folder at the volume root holds all the volumes, images, subvolumes, etc. and I did copy that over.
Copying over the files wouldn’t be enough. You would actually need to create the subvolumes, e.g. btrfs subvolume create subvolume_name.
Do you happen to know if I find the snapshot folder and download it, will there be anything recoverable? Or would it just be like, hashes and unintelligble stuff?
Unfortunately, I am not familiar enough with how Synology does things, but a btrfs snapshot will just appear as normal directory with the files/directories in it. If Synology isn’t using btrfs for the snapshoting, I’m not sure what you’ll find.
I’m running it at the root of the volume. I have volume1 which is my SHR array and volume 2 which is just an nvme, i believe in JBOD configuration. Synology mounts shared folders as the main way to handle storage. I’m hopeful I’ll be able to rescue the snapshot then. It’s just not mounted where it would be if the shared folder it corresponds to existed. I want to try creating a new shared folder with the same name but i worry 1. it would be for nothing and 2, it would delete the snapshot somehow.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.
Rules:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
selfh.st Newsletter and index of selfhosted software and apps
Yes I can SSH in. I think the snapshot exists but is not mounted as a btrfs subvolume. In storage manager, it gives an overview of what’s taking up space on your volume, and snapshots shows it taking up space so I’m certain it’s there. the subvolume list on my other volume is showing the other snapshots I’ve created for other shared folders though.
from the research I did, the @docker folder at the volume root holds all the volumes, images, subvolumes, etc. and I did copy that over.
Do you happen to know if I find the snapshot folder and download it, will there be anything recoverable? Or would it just be like, hashes and unintelligble stuff?
Is it not listed when you try running
btrfs subvolume list .? You might need to change the.to a path that is on the array.Copying over the files wouldn’t be enough. You would actually need to create the subvolumes, e.g.
btrfs subvolume create subvolume_name.Unfortunately, I am not familiar enough with how Synology does things, but a btrfs snapshot will just appear as normal directory with the files/directories in it. If Synology isn’t using btrfs for the snapshoting, I’m not sure what you’ll find.
I’m running it at the root of the volume. I have volume1 which is my SHR array and volume 2 which is just an nvme, i believe in JBOD configuration. Synology mounts shared folders as the main way to handle storage. I’m hopeful I’ll be able to rescue the snapshot then. It’s just not mounted where it would be if the shared folder it corresponds to existed. I want to try creating a new shared folder with the same name but i worry 1. it would be for nothing and 2, it would delete the snapshot somehow.