[OpenAFS] No buffer space available

Stephan Wiesand stephan.wiesand@desy.de
Fri, 11 Oct 2013 17:36:52 +0200

On Jul 23, 2013, at 18:40 , Andrew Deason <adeason@sinenomine.net> =

> On Tue, 23 Jul 2013 13:11:17 +0200
> Hans-Werner Paulsen <hans@MPA-Garching.MPG.DE> wrote:
>> sometimes creating a file (using different programs) fails with the
>> error message "No buffer space available". This is on amd64_linux26
>> with OpenAFS 1.6.2 (both client and server). Any idea?
> I don't see anywhere we'd be generating that error code (ENOBUFS), and =
> can't see how it would show up that way if we got it back from a =
> or something. Do you have any idea if the machine is under a lot of =
> or memory pressure, or if the directory has a lot of entries in it?

To add a data point:

I just encountered this while copying two rather small files for the = release from here (~ Berlin) to PENN-CENTRAL.SRV.CS.CMU.EDU.

% cp /tmp/openafs-release-* . -iv  =20
`/tmp/openafs-release-fedora-' -> =
cp: cannot create regular file =
`./openafs-release-fedora-': No buffer space =
`/tmp/openafs-release-rhel-' -> =

So the first one failed. The destination file was created, but had =
length 0. The very next attempt succeeded. It's the first time I ever =
encountered this problem. Client is SL6.4, 2.6.32-358.18.1.el6.x86_64, =
OpenAFS (built against the -358.el6 kernel - which I know voids =
my warranty ;-), disk cache on ext4.

Not reproducible, nothing in the logs or the kernel message buffer.

The client was not under any load and has 12 GB of free (really unused) =
RAM. The server seemed not to be busy either. The only special condition =
is the long distance between client and server.

No showstopper, and probably very hard to track down without a =

Stephan Wiesand
Platanenallee 6
15732 Zeuthen, Germany