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
On Wed, 4 Apr 2007, Gerry Reno wrote:
Check:
/proc/sys/fs/file-nr
/proc/sys/fs/file-max
to increase:
echo NNNNNN > /proc/sys/fs/file-max
Gerry
Brent A Nelson wrote:
I put a 2-node GlusterFS mirror into use internally yesterday, as GlusterFS
was looking pretty solid, and I rsynced a whole bunch of stuff to it.
Today, however, an ls on any of the three clients gives me:
ls: /backup: Too many open files
It looks like glusterfsd hit a limit. Is this a bug (glusterfs/glusterfsd
forgetting to close files; essentially, a file descriptor leak), or do I
just need to increase the limit somewhere?
Thanks,
Brent
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxx
http://lists.nongnu.org/mailman/listinfo/gluster-devel
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxx
http://lists.nongnu.org/mailman/listinfo/gluster-devel
