-
Notifications
You must be signed in to change notification settings - Fork 136
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cloning files on BTRFS read-only snapshots doesn't work #195
Comments
I guess you used a command like this? $ rmlint -c sh:link subvol/ And tried to execute $ ./rmlint.sh If so, what would your expected behaviour be? I see that the error message is not very nice, but, as I understand you, you're suggesting that |
Indeed I used this command line:
The rmlint "clone" command, should be able to operate on read-only snapshots and not giving an error, but perhaps with an option/flag to make sure that the user knows what he is doing (but cloning is quite safe, from what I understand). |
Thanks @saintger for finding this. It doesn't seem well documented anywhere but here's what I found by trial-and-error and reference to markfasheh/duperemove@fe67b7c:
Branch https://github.com/SeeSpotRun/rmlint/tree/btrfs-clone-readonly should be able to deduplicate read-only snapshots.
Usage via rmlint.sh:
|
@SeeSpotRun Thanks it seems to work perfectly ! |
I merged @SeeSpotRun's changes into the |
Have updated docs to include --btrfs-clone [-r](probably breaks translations) |
Trying to deduplicate/clone files which are on BTRFS read-only snapshots, return an error:
If it helps, duperemove has a special flag ("-A") to manage this situation:
https://github.com/markfasheh/duperemove/blob/master/filerec.c#L405-L434
The text was updated successfully, but these errors were encountered: