-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Issues: gluster/glusterfs
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
'transport.socket.bind-address' is not taking effect when starting vol
#4428
opened Nov 4, 2024 by
zhangxyue
Assertion failed: !(*take_lock) will cause stale inodelk and block subsequent IO
#4425
opened Oct 22, 2024 by
chen1195585098
Program with Multiple Syscalls Hangs When Executed on GlusterFS
#4411
opened Sep 11, 2024 by
l392zhan
enabling "bitrot" for one volume triggers "oneshot crawl" for all already enabled volumes
#4408
opened Sep 10, 2024 by
pbiering
[GEOREPLICATION] gsyncd is broken due to ConfigParser's
readfp()
being removed in Python 3.12
#4403
opened Aug 28, 2024 by
hunter86bg
After shard is enabled, the size of the copied file is inconsistent with the original file
#4401
opened Aug 14, 2024 by
jifengzhou
Feature Request - Write unique identifier to each brick to halt if brick is mounted in incorrect location
#4396
opened Jul 29, 2024 by
edrock200
performance.nl-cache=on result in error messages __nlc_inode_clear_entries Assertion failed
#4390
opened Jul 4, 2024 by
pbiering
Blocking ports 49147-49151 unexpectedly blocks connection to peers
#4389
opened Jul 4, 2024 by
BertrandBordage
Gluster expects bricks to be hosted on newly peer-probed machine...
#4386
opened Jul 1, 2024 by
babipanghang
Previous Next
ProTip!
Follow long discussions with comments:>50.