2f04e20627
A user on the forum was seeing the error "bad message", which was not very helpful. This case from the ext4 filesystem using the code EBADMSG to indicate it detected an invalid CRC, suggesting disk corruption. This change adds some explanatory information about probable disk corruption to all errors coming from the (*blobInfo).Stat() call, which is where storagenode fs corruption problems will usually manifest. Refs: https://github.com/storj/storj/issues/5375 Change-Id: I87f4a800236050415c4191ef1a0fc952f9def315 |
||
|---|---|---|
| .. | ||
| blob.go | ||
| dir_test.go | ||
| dir_unix.go | ||
| dir_windows.go | ||
| dir.go | ||
| error.go | ||
| errors_other.go | ||
| errors_unix.go | ||
| store_test.go | ||
| store.go | ||