[Pvfs2-developers] pvfs2-cli can't identify protocol

[Rob Ross]

Hi Amit,

What version of PVFS is this?

What does the output of netstat -tan look like?

Thanks,

Rob

On Jan 7, 2009, at 2:03 PM, Kumar, Amit H. wrote:

> Hello All,
> I am trying to understand the following output from “lsof”.
> All/most of our compute nodes (pvfs2 clients) have the following  
> output as reported by “lsof”
> Few of the pvfs2-client nodes have greater than 1024 open sockets  
> for just the pvfs2-client process. Current ulimit for maximum number  
> of open files per process is set to 1024 on all of our computer  
> nodes. I see this as a potential performance problem. I was  
> wondering if any of you can help me interpret the output and fix any  
> issues that this could be causing.
> <lsof output>
> ……………
> pvfs2-cli 27278      root  121u     sock                 
> 0,5            13574284 can't identify protocol
> pvfs2-cli 27278      root  122u     sock                 
> 0,5            13574285 can't identify protocol
> pvfs2-cli 27278      root  123u     sock                 
> 0,5            13574286 can't identify protocol
> pvfs2-cli 27278      root  124u     sock                 
> 0,5            13574287 can't identify protocol
> pvfs2-cli 27278      root  125u     sock                 
> 0,5            13574288 can't identify protocol
> pvfs2-cli 27278      root  126u     sock                 
> 0,5            13574289 can't identify protocol
> pvfs2-cli 27278      root  127u     sock                 
> 0,5            13574290 can't identify protocol
> pvfs2-cli 27278      root  128u     sock                 
> 0,5            13574291 can't identify protocol
> pvfs2-cli 27278      root  129u     sock                 
> 0,5            13574292 can't identify protocol
> pvfs2-cli 27278      root  130u     sock                 
> 0,5            13574303 can't identify protocol
> pvfs2-cli 27278      root  131u     sock                 
> 0,5            13574304 can't identify protocol
> pvfs2-cli 27278      root  132u     sock                 
> 0,5            13574326 can't identify protocol
> pvfs2-cli 27278      root  133u     sock                 
> 0,5            13574327 can't identify protocol
> pvfs2-cli 27278      root  134u     sock                 
> 0,5            13574328 can't identify protocol
> pvfs2-cli 27278      root  135u     sock                 
> 0,5            13574329 can't identify protocol
> pvfs2-cli 27278      root  136u     sock                 
> 0,5            13574330 can't identify protocol
> pvfs2-cli 27278      root  137u     sock                 
> 0,5            13574331 can't identify protocol
> pvfs2-cli 27278      root  138u     sock                 
> 0,5            13574332 can't identify protocol
> pvfs2-cli 27278      root  139u     sock                 
> 0,5            13574333 can't identify protocol
> pvfs2-cli 27278      root  140u     sock                 
> 0,5            13574334 can't identify protocol
> pvfs2-cli 27278      root  141u     sock                 
> 0,5            13574336 can't identify protocol
> pvfs2-cli 27278      root  142u     sock                 
> 0,5            13574337 can't identify protocol
> pvfs2-cli 27278      root  143u     sock                 
> 0,5            13574338 can't identify protocol
> pvfs2-cli 27278      root  144u     sock                 
> 0,5            13574344 can't identify protocol
> pvfs2-cli 27278      root  145u     sock                 
> 0,5            13574345 can't identify protocol
> pvfs2-cli 27278      root  146u     sock                 
> 0,5            13574346 can't identify protocol
> pvfs2-cli 27278      root  147u     sock                 
> 0,5            13574357 can't identify protocol
> …………
> </lsof output>
> Thank you,
> Amit
>
>
>
> _______________________________________________
> Pvfs2-developers mailing list
> Pvfs2-developers at beowulf-underground.org
> http://www.beowulf-underground.org/mailman/listinfo/pvfs2-developers