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

HDD read write failure on single array #777

Open
lrcressy opened this issue Apr 10, 2024 · 2 comments
Open

HDD read write failure on single array #777

lrcressy opened this issue Apr 10, 2024 · 2 comments
Labels
question Not a bug, clarifications, undocumented behaviour

Comments

@lrcressy
Copy link

When a disk fails it would be nice to be able to force a removal of a device on a single array when the copy fails because of the drive failure. I just bought a WD 20 T drive which failed after 4 days usage. Because of hardware failure I had to recreate the entire filesystem.

@Forza-tng
Copy link
Contributor

@lrcressy it's a very unfortunate thing that happened to you. When it comes to the single profile, there are several things that makes what you want very difficult. If you were using single profile for metadata, then the likelihood to survive a disk failure is near 0, because some metadata will undoubtedly be on the broken device. If you have raid1 profile, the metadata will survive one failed disk, and any data on that disk will not be readable. You could leave the filesystem in this state until a replacement is available. Any files (could be a lot, or most) with missing data will have to be recreated from backups, but the filesystem should be recoverable.

@lrcressy
Copy link
Author

lrcressy commented Apr 11, 2024 via email

@kdave kdave added the question Not a bug, clarifications, undocumented behaviour label Apr 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Not a bug, clarifications, undocumented behaviour
Projects
None yet
Development

No branches or pull requests

3 participants