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

It would be a good idea to document what would be the increased risk of failure resulting from selecting a subset of available blockdevs to write metadata to #45

Open
mulkieran opened this issue Jul 6, 2017 · 2 comments
Assignees

Comments

@mulkieran
Copy link
Member

No description provided.

@agrover
Copy link
Contributor

agrover commented Jul 6, 2017

How do you mean? If we have a 1000 disk pool for example and write metadata to 10, if those 10 somehow end up not being in the pool after a reboot, then we will get stale metadata and that could be extremely bad.

@mulkieran
Copy link
Member Author

Yes. That's one failure mode. But we should understand it in terms of probabilities, like people are able to do with RAID.

@mulkieran mulkieran self-assigned this Feb 21, 2024
@mulkieran mulkieran moved this to To do in 2024June May 28, 2024
@mulkieran mulkieran removed this from 2024June Jul 3, 2024
@mulkieran mulkieran moved this to Todo in 2024July Jul 3, 2024
@mulkieran mulkieran removed this from 2024July Aug 5, 2024
@mulkieran mulkieran moved this from Todo to In Progress in 2024August Aug 5, 2024
@mulkieran mulkieran moved this from In Progress to Todo in 2024August Aug 5, 2024
@mulkieran mulkieran removed this from 2024August Sep 5, 2024
@mulkieran mulkieran moved this to Todo in 2024September Sep 5, 2024
@mulkieran mulkieran added this to the Metadata-related milestone Sep 18, 2024
@mulkieran mulkieran removed this from 2024September Oct 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Todo
Development

No branches or pull requests

2 participants