Brent A Nelson wrote:
I already looked there, and my file-nr allocated is much lower than
file-max. It might be hitting some other limit, perhaps even a limit
imposed by the bash that started glusterfsd. Still it really seems
like there shouldn't be so many allocated file descriptors lying
around (no files should currently be open, and rsync wouldn't have
left large numbers open at the same time, I assume), so I think it's a
bug where GlusterFS is not closing all the file descriptors it opens
or allocates.
Thanks,
Brent
Paste the output of 'uname -a' from a shell that you would normally
start glusterfsd. What distro are you using?
_______________________________________________
Gluster-devel mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/gluster-devel
