[OpenAFS] kernel: afs_NewVCache: warning none freed, using 4000 of 4000

Ken Aaker kenaaker@silverbacksystems.com
Tue, 06 Mar 2007 13:11:45 -0600


Here's a sample from the client machine with the problem...

Ken

grep "refcnt     [0]" /tmp/sif_cmdebug_long.txt | wc -l
0

grep "refcnt     [1]" /tmp/sif_cmdebug_long.txt | wc -l
0

grep "refcnt     [2]" /tmp/sif_cmdebug_long.txt | wc -l
3972

grep "refcnt     [3]" /tmp/sif_cmdebug_long.txt | wc -l
24

grep "refcnt     [4]" /tmp/sif_cmdebug_long.txt | wc -l
2

grep "refcnt     [5]" /tmp/sif_cmdebug_long.txt | wc -l
0

grep "refcnt     [0-9]" /tmp/sif_cmdebug_long.txt | wc -l
3998

-------------------------------------------------------
Lock afs_xvcache status: (none_waiting)
Lock afs_xdcache status: (none_waiting)
Lock afs_xserver status: (none_waiting)
Lock afs_xvcb status: (none_waiting)
Lock afs_xbrs status: (none_waiting)
Lock afs_xcell status: (none_waiting)
Lock afs_xconn status: (none_waiting)
Lock afs_xuser status: (none_waiting)
Lock afs_xvolume status: (none_waiting)
Lock puttofile status: (none_waiting)
Lock afs_ftf status: (none_waiting)
Lock afs_xcbhash status: (none_waiting)
Lock afs_xaxs status: (none_waiting)
Lock afs_xinterface status: (none_waiting)
Lock afs_xosi status: (none_waiting)
Lock afs_xsrvAddr status: (none_waiting)
Lock afs_xvreclaim status: (none_waiting)
** Cache entry @ 0xdcdf9580 for 2.536870951.6105.3870355 [sbsroch.com]
            2048 bytes  DV           39  refcnt     2
    callback dea1e480   expires 1173206220
    0 opens     0 writers
    normal file
    states (0x0)
** Cache entry @ 0xd3b1dd00 for 2.536870951.9177.6560125 [sbsroch.com]
            2048 bytes  DV           13  refcnt     2
    callback dea1e480   expires 1173205580
    0 opens     0 writers
    normal file
    states (0x0)
** Cache entry @ 0xd1818a80 for 2.536870951.985.4554001 [sbsroch.com]
            2048 bytes  DV           25  refcnt     2
    callback dea1e480   expires 1173217356
    0 opens     0 writers
    normal file
    states (0x1), stat'd
** Cache entry @ 0xc77f5800 for 2.536870951.8153.6557130 [sbsroch.com]
            2048 bytes  DV           91  refcnt     2
    callback dea1e480   expires 1173201996
    0 opens     0 writers
    normal file
    states (0x0)
** Cache entry @ 0xcdf53580 for 2.536870951.22489.3650163 [sbsroch.com]
            2048 bytes  DV           18  refcnt     2
    callback dea1e480   expires 1173217740
    0 opens     0 writers
    normal file
    states (0x1), stat'd
** Cache entry @ 0xd2a5a800 for 2.536870951.7129.3871389 [sbsroch.com]
            2048 bytes  DV           78  refcnt     2
    callback dea1e480   expires 1173215052
    0 opens     0 writers
    normal file
    states (0x1), stat'd
** Cache entry @ 0xd5cd6300 for 2.536870951.4057.268226 [sbsroch.com]
            2048 bytes  DV            2  refcnt     2
    callback dea1e480   expires 1173199436
    0 opens     0 writers
    normal file
    states (0x0)
** Cache entry @ 0xc5e33300 for 2.536870951.75738.3545499 [sbsroch.com]
            1489 bytes  DV           40  refcnt     2
    callback dea1e480   expires 1173199052
    1 opens     1 writers
    normal file
    states (0x0)



Derrick J Brashear wrote:
> On Tue, 6 Mar 2007, Ken Aaker wrote:
>
>> Derrick J Brashear wrote:
>>> On Tue, 6 Mar 2007, Ken Aaker wrote:
>>>
>>>> Ok, I've saved the outputs from cmdebug -long for each of my servers.
>>>
>>> It's the client with whichever which gets the NewVCache error we want
>>> the cmdebug info from, and it better have about 4000 lines with a
>>> refcnt greater than 0 (so posting it is probably bad)
>> The cmdebug command  was run on the client that's having trouble.
>> cmdebug -long complained if I didn't supply a server name.
>
> The servername if you run it on the client with trouble is "localhost" :)
>
>> I can digest the files a little.... Once I get these messages, it seems
>> like any references to files not in the cache generate odd failures in
>> applications, and the problem is cured by a reboot...
>
> Right, that's expected. No more files means....
>
> _______________________________________________
> OpenAFS-info mailing list
> OpenAFS-info@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-info