-
Notifications
You must be signed in to change notification settings - Fork 18
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
Issue with quota #68
Comments
It's known btrfs feature (cough, cough). See #38 You should try Linux kernels >=4.20 |
There is also experimental branch (#60) of buttersink that uses timestamps to select base snapshots and do not rely on quotas. I do not have time to bring it to the master. |
Thanks, I saw the experimental branch but I wasn't sure if it works for ssh
remote, and should I use the experimental branch on both the source and
remote ?
As for switching to kernels >=4.20, sadly it's not available on debian
stretch now and I'm not willing to go experimental on that machine...
Le lun. 18 mars 2019 à 05:18, eugene-bright <[email protected]> a
écrit :
… There is also experimental branch (#60
<#60>) of buttersink that
uses timestamps to select base snapshots and do not rely on quotas. I do
not have time to bring it to the master.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#68 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAuwQzVVSgnAz7jfqBR6eg4LG5udkvCFks5vX1nzgaJpZM4b4kb3>
.
|
If you are going to give my branch a try you should update both sides as new field was introduced in RPC return record ( |
I've seen severall mention online of issues with btrfs quotas, is there a way to make buttersink without using quota ?
I'm trying to sink to a remote ssh and by activating quota on that machine it almost always crash at some point with btrfs-cleaner using all cpu and memory... (lot of snapshots and arround 12TB of storage).
The text was updated successfully, but these errors were encountered: