[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
How to investigate ENOBUFS?
I resumed my work on perfused (FUSE to PUFFS bridge). The latest stress-test
is to build a NetBSD release on a glusterfs filesystem.
After some time, operations on the filesystem hang, and perfused says once:
perfused: perfuse_writeframe: send retunred -1: No buffer space available
: No buffer space available
The filesystem will never recover. As I understand, this happens because
some socket has pending data that is never readen. Do I have a way to
discover what socket is holding buffer space? And is there a way to see how
much buffer space is allocated and how much remain, by the way?
Main Index |
Thread Index |