Axel Burri

It's less of a technical restriction (btrfs should be able to cope with that), here's some reasons that come into my mind: - If you do that, you are making...

Sorry don't have an answer for this. Besides btrbk snapshots there are no read-only snapshots on my system. `btrbk archive` comes closest, but sadly needs btrbk-style filenames to work. Now...

nothing really bad can happen, the locking merely makes sure that no errors occur. E.g. btrbk might print errors if the same backup is to be created, by running `btrbk...

something like this might come in the future, but it might get hard to know what to do exactly: do you just want to "btrfs delete" it? what if it's...

According to the bug report, this is now fixed upstream. Can you confirm this?

Thanks for the suggestion, added "enhancement" label. I'm not sure if this is worth the effort: this adds redundancy, and implies a new framework for checking these symlink, and keeping...

Looks like CentOS does not run btrbk as a perl script. Maybe related to #307. Does it help if you change the shabang (like here: 175049fa11198654e643c03721ee493430ce4116)?

I think the issue is ancient perl version in CentOS 7 (according to pkgs.org it's 5.16.3: https://pkgs.org/download/perl). Can you please provide me the exact btrbk version you were running (commit...

Thanks for the input. I guess it's due to historical growth of btrbk code, and I'll have to refactor the places where the locking is done. Actually it's being too...

i'm not sure if this completely implements it, looks promising though. I suspect there might be other places in the code which rely on simple `$snapshot_name`. not sure though, will...