[OpenAFS] Error in enumerating set cmfx (errno = 2)

[Lester Barrows]

Hi Jeffrey,

Thanks for the response. The AFS servers and clients are running OpenAFS 
1.2.13 on Linux clients (two Redhat EL 3 servers, one MDK 8.1 server, and 
various clients.) 

The firewall allows them to be sent as long as the client initiates the 
connection. AFS typically works fine, however in this case it seems that 
there are issues with a large file transfer/reorganization happening on one 
of the servers.

Let me know if there's anything else I can add that would be of help. I have a 
client in this state that I'm going to leave in this state until I can 
determine the cause. :)

Regards,

Lester Barrows
Asani Solutions, LLC
Code TI Systems Group
NASA Ames Research Center
Voice: 650-604-2639

"Jura rapelcgvba vf bhgynjrq, bayl bhgynjf jvyy unir cevinpl."

On Tuesday 29 March 2005 15:28, Jeffrey Altman wrote:
> Lester:
>
> Some things which would be helpful to know:
>
> * what version(s) are the AFS servers?
>
> * what version(s) are the AFS clients?
>
> * does the firewall allow arbitrary UDP packets to be sent to internal
>    IP addresses on port 7001?
>
> Jeffrey Altman
>
> Lester Barrows wrote:
> > Hi All,
> >
> > I've been having an issue with some clients no longer being able to
> > access a fileserver when the server is put under a high load, typically
> > by transferring many small files. It's almost as if the server is
> > ignoring the client. This condition can only be remedied by rebooting the
> > client computer, shutting down the AFS client software doesn't help.
> > Neither does restarting the fs, volserver or entire AFS service on the
> > server.
> >
> > I've been able to find a few error messages, but this one (found through
> > fstrace) was particularly puzzling as I'm not certain what it means:
> >
> > fstrace lslog cmfx
> > Logs for set 'cmfx':
> > Error in enumerating set cmfx (errno = 2)
> >
> > Additionally, the following message comes up for various hosts in the
> > server's FileLog logfile. Clients that exhibit the issue show up in the
> > log. There is a firewall between the server and the client which is
> > probably part of the issue, however the clients typically work well
> > enough. I would expect restarting the AFS client service alone would
> > restore connectivity if the firewall lacking a connection was the
> > problem. The network incidentally is not a reserved range, the IP
> > addresses are fully routable. Client-initiated connections from any port
> > are allowed.
> >
> > Tue Mar 29 07:55:34 2005 ProbeUuid failed for host xxx.xxx.xxx.xxx:7001
> >
> > Any ideas?
> >
> > Regards,
> >
> > Lester Barrows
> > Asani Solutions, LLC
> > Code TI Systems Group
> > NASA Ames Research Center
> > _______________________________________________
> > OpenAFS-info mailing list
> > OpenAFS-info@openafs.org
> > https://lists.openafs.org/mailman/listinfo/openafs-info