You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When hostd encounters a sector read/write error on a volume, it appears to mark that volume as "unavailable" for an unknown amount of time. Sometimes these errors are transient, e.g. a remote file server rebooting or the like. It would be helpful to have some control that would trigger hostd to re-check the availability of the volume when the operator believes it should be available again.
Version
v1.1.0
What operating system are you running (e.g. Ubuntu 22.04, macOS, Windows 11)?
Pop!_OS 22.04 / kernel 6.8.0
Anything else?
No response
The text was updated successfully, but these errors were encountered:
The workaround is complete removal of "wounded" volumes, and creating new.
Very weird, admin time and CPU consuming process for specialized data hosting software project...
Restarting hostd after the volume is available again will reload the volumes and workaround the issue as described. There’s no need to remove the volume.
Description
When
hostd
encounters a sector read/write error on a volume, it appears to mark that volume as "unavailable" for an unknown amount of time. Sometimes these errors are transient, e.g. a remote file server rebooting or the like. It would be helpful to have some control that would trigger hostd to re-check the availability of the volume when the operator believes it should be available again.Version
v1.1.0
What operating system are you running (e.g. Ubuntu 22.04, macOS, Windows 11)?
Pop!_OS 22.04 / kernel 6.8.0
Anything else?
No response
The text was updated successfully, but these errors were encountered: