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
Projects

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 added this to To do in 2024February via automation Feb 21, 2024
@mulkieran mulkieran self-assigned this Feb 21, 2024
@mulkieran mulkieran removed this from To do in 2024February Mar 5, 2024
@mulkieran mulkieran added this to To do in 2024March via automation Mar 5, 2024
@mulkieran mulkieran removed this from To do in 2024March Apr 2, 2024
@mulkieran mulkieran added this to To do in 2024April via automation Apr 2, 2024
@mulkieran mulkieran removed this from To do in 2024April Apr 29, 2024
@mulkieran mulkieran added this to To do in 2024May via automation Apr 29, 2024
@mulkieran mulkieran removed this from To do in 2024May May 28, 2024
@mulkieran mulkieran added this to To do in 2024June via automation May 28, 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