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
example of a good issue report: #1005
example of a bad issue report: #1008
Describe the bug
Some files seem to become unreadable, getting EIO when trying to read them.
Also seems to cause weed backup memory usage to grow without bound unless I limit it in systemd.
Logs are absolutely full of failures to read a certain volume.
System Setup
Kubernetes Helm chart - initially set up a year or two ago and I've gone and modified it heavily. Easist is probably to dump all the Kubernetes configs in YAML format, which I did here...
Sponsors SeaweedFS via Patreon https://www.patreon.com/seaweedfs
Report issues here. Ask questions here https://stackoverflow.com/questions/tagged/seaweedfs
Please ask questions in https://github.com/seaweedfs/seaweedfs/discussions
example of a good issue report:
#1005
example of a bad issue report:
#1008
Describe the bug
Some files seem to become unreadable, getting
EIO
when trying to read them.Also seems to cause
weed backup
memory usage to grow without bound unless I limit it insystemd
.Logs are absolutely full of failures to read a certain volume.
System Setup
Kubernetes Helm chart - initially set up a year or two ago and I've gone and modified it heavily. Easist is probably to dump all the Kubernetes configs in YAML format, which I did here...
https://gist.github.com/werdnum/dab4ebfbf7968efd6d64cb94a6f20bc9
Expected behavior
Able to read files
Screenshots
Not applicable but the logs are absolutely packed with this:
Filer:
Some possibly related stuff in volume server logs:
For some reason I can't find matching entries for the same volume number in both filer & volume, but it might just not be logged correctly?
Grepping over all logs for the signatures, it seems like the corruption is only in a few places...
❯ for n in 0 1 2 3 4 5 6; do kubectl logs -n seaweedfs seaweedfs-volume-${n} | grep needle_read.go
done | gh gist create -
✓ Created gist
https://gist.github.com/werdnum/baaae30dc9efb6eb0d10dac7f15a291f
With context: https://gist.github.com/werdnum/a3a0fc21f56c51a04572716ff015d5dc
Volume 4416 is an erasure-coded volume. I tried to decode it...
(note that it complains each time about a different shard being missing)
ec.rebuild
returns in under a second so I don't think it's doing anything.Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: