Skip to content
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

stuck and eats 100% cpu #38

Closed
gaetanquentin opened this issue Feb 5, 2017 · 4 comments
Closed

stuck and eats 100% cpu #38

gaetanquentin opened this issue Feb 5, 2017 · 4 comments

Comments

@gaetanquentin
Copy link

sometimes it is stuck in infinite loop and eats 100%cpu.

Can't kill it (KILL -9 do nothing), and a strace shows nothing, so it seems it does not call sys calls at all.

@AmesCornish
Copy link
Owner

Hard to debug this without more context. It sounds like a hang in the btrfs subsystem, maybe during send or receive. I'd check that you have the latest btrfs-progs, and a recent kernel. It could also be due to corruption in the btrfs file system.

@eugene-bright
Copy link
Collaborator

eugene-bright commented Jun 23, 2018

I'm experiencing such kind of things on snapshot deletion.
One old email thread fully describes my symptoms.

@eugene-bright
Copy link
Collaborator

Buttersink relies on btrfs quota feature to estimate diff sizes. If btrfs quota is disabled then it will be enabled by buttersink (but it also seems to be enabled by default on newly created FS).
Snapshot deletion can cause performance issues if quote feature is enabled.
https://www.reddit.com/r/btrfs/comments/4qz1qd/problems_with_btrfs_quota/

It looks to be a btrfs bug.
We should workaround it by adding an option to buttersink to disable any size estimation.

@eugene-bright
Copy link
Collaborator

eugene-bright commented Jun 26, 2018

Quoting developers conversation
https://www.spinics.net/lists/linux-btrfs/msg74737.html

Snapshot creation and backref walk (used in qgroup, relocation and
extent deletion), are two conflicting workload in fact.

eugene-bright added a commit to eugene-bright/buttersink that referenced this issue Jul 11, 2018
Based on existing work AmesCornish#29.

Use estimation option twice to disable relying on quotas (`-ee`).

Lacking of snapshot size information
cause crazy diff paths on current algorithm.

Closes: AmesCornish#29
Resolves: AmesCornish#38
eugene-bright added a commit to eugene-bright/buttersink that referenced this issue Jul 12, 2018
Based on existing work AmesCornish#29.

Use estimation option twice to disable relying on quotas (`-ee`).

Lacking of snapshot size information
cause crazy diff paths on current algorithm.

Closes: AmesCornish#29
Resolves: AmesCornish#38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants