Snapshots should be a safety feature meaning that the user can use them to try something safe in the knowledge that they can revert back. In my case there always seems to be a reason why this doesn't work as it should.
Here's an example:
I had created a more recent snapshot but it can't roll back to where I need it because there was a more recent one. I remove that so that I can roll back; here's what happens when I try...
Roll back - nope you can't do that there is an invisible force stopping you.
I'm on the current version of everything - and I tend to get either this or a message saying can't unmount the current one because the resource is busy.
About 8 out of 10 it works ok, I think tends to be when you have had more recent snapshots. 8 out of 10 isn't good enough for the chances of walking safely across the road and its not good enough here either.
I also have had issues when there seem to be orphaned disks for another long gone container 119 flapping about in the background.
this might help:
rpool/data/subvol-119-disk-0@cleardown 251G - 253G -
rpool/data/subvol-119-disk-0@insync 230G - 232G -
rpool/data/subvol-119-disk-0@__migration__ 0B - 1.77G -
rpool/data/subvol-119-disk-1@cleardown 7.43M - 844M -
rpool/data/subvol-119-disk-1@insync 243K - 844M -
seems there's some junk laying around because it failed previously. Very annoying. Does anyone know what incantation I can call up to fix the situation?
I have a theory in this case it may be bacause one of the disks did not have backup checked so I went backwards and forwards to get what I need, but its generally buggy and messes things up for me frequently.
Here's an example:
I had created a more recent snapshot but it can't roll back to where I need it because there was a more recent one. I remove that so that I can roll back; here's what happens when I try...
Roll back - nope you can't do that there is an invisible force stopping you.
I'm on the current version of everything - and I tend to get either this or a message saying can't unmount the current one because the resource is busy.
About 8 out of 10 it works ok, I think tends to be when you have had more recent snapshots. 8 out of 10 isn't good enough for the chances of walking safely across the road and its not good enough here either.
I also have had issues when there seem to be orphaned disks for another long gone container 119 flapping about in the background.
this might help:
rpool/data/subvol-119-disk-0@cleardown 251G - 253G -
rpool/data/subvol-119-disk-0@insync 230G - 232G -
rpool/data/subvol-119-disk-0@__migration__ 0B - 1.77G -
rpool/data/subvol-119-disk-1@cleardown 7.43M - 844M -
rpool/data/subvol-119-disk-1@insync 243K - 844M -
seems there's some junk laying around because it failed previously. Very annoying. Does anyone know what incantation I can call up to fix the situation?
I have a theory in this case it may be bacause one of the disks did not have backup checked so I went backwards and forwards to get what I need, but its generally buggy and messes things up for me frequently.
