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

enabling "bitrot" for one volume triggers "oneshot crawl" for all already enabled volumes #4408

Open
pbiering opened this issue Sep 10, 2024 · 2 comments

Comments

@pbiering
Copy link

pbiering commented Sep 10, 2024

Description of problem:

enabling "bitrot" for one volume triggers "oneshot crawl" for all already configured (and passed run) volumes

The exact command to reproduce the issue:

gluster volume bitrot volume2 enable

The full output of the command that failed:

n/a

Expected results:

"oneshot crawl" will only start immediately on new enabled volume, not re-run on already configured (and passed) volumes again

- The operating system / glusterfs version:

EL9 / 10.5

@pbiering
Copy link
Author

same happen after disable, next oneshot over all for bitrot configured volumes is started again.

gluster volume bitrot volume2 disable

@pbiering
Copy link
Author

pbiering commented Oct 4, 2024

seel also after upgrade to 11.1

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

1 participant