vnodes - is there a leak? where are they going?

I have two servers, both running 4.10 of within a few days (Aug 5 for 
venus, Aug 7 for neptune) ... both running jail environments ... one with 
~60 running, the other with ~80 ... the one with 60 has been running for 
~25 days now, and is at the border of running out of vnodes:

Aug 31 20:58:00 venus root: debug.numvnodes: 519920 - debug.freevnodes: 11058 - debug.vnlru_nowhere:
256463 - vlrup
Aug 31 20:59:01 venus root: debug.numvnodes: 519920 - debug.freevnodes: 13155 - debug.vnlru_nowhere:
256482 - vlrup
Aug 31 21:00:03 venus root: debug.numvnodes: 519920 - debug.freevnodes: 13092 - debug.vnlru_nowhere:
256482 - vlruwt

while the other one has been up for ~1 days, but is using alot less, for 
more processes:

Aug 31 20:58:00 neptune root: debug.numvnodes: 344062 - debug.freevnodes: 208655 -
debug.vnlru_nowhere: 0 - vlruwt
Aug 31 20:59:00 neptune root: debug.numvnodes: 344062 - debug.freevnodes: 208602 -
debug.vnlru_nowhere: 0 - vlruwt
Aug 31 21:00:03 neptune root: debug.numvnodes: 344062 - debug.freevnodes: 208319 -
debug.vnlru_nowhere: 0 - vlruwt

I've tried shutting down all of the VMs on venus, and umount'd all of the 
unionfs mounts, as well as the one nfs mount we have ... the above #s are 
after the VMs (and mounts are recreated ...

Now, my understanding of the vnodes is that for every file opened, a vnode 
is created ... in my case, since I'm using unionfs, there are two vnodes 
per file ... if it possible that there are 'stale' vnodes that aren't 

Re: vnodes - is there a leak? where are they going?

As a follow up, looking at vmstat -m .. specifically the work that David 
did on seperating the union vs regular vnodes:

   UNION mount    60     2K      3K204800K      162    0     0  32
        undcac     0     0K      1K204800K343638713    0     0  16
        unpath 13146   227K   1025K204800K 43541149    0     0  16,32,64,128
   Export Host     1     1K      1K204800K      164    0     0  256
        vnodes   141     7K      8K204800K      613    0     0  16,32,64,128,256

Why does 'vnodes' show only 141 InUse?  Or, in this case, should I be 
looking at:

      FFS node496600124150K 127870K204800K401059293    0     0  256

496k FFS nodes, if I'm reading right?

vs neptune, which is showing only:

      FFS node300433 75109K  80257K204800K  3875307    0     0  256

On Tue, 31 Aug 2004, Marc G. Fournier wrote:

>
> I have two servers, both running 4.10 of within a few days (Aug 5 for venus, 
> Aug 7 for neptune) ... both running jail environments ... one with ~60 
> running, the other with ~80 ... the one with 60 has been running for ~25 days 
> now, and is at the border of running out of vnodes:
>
> Aug 31 20:58:00 venus root: debug.numvnodes: 519920 - debug.freevnodes: 11058 

Re: vnodes - is there a leak? where are they going?

Hrmmm, maybe I'm mis-reading all of this, and going down the wrong paths 
here, so hopefully someone will correct if I am ... but, for now ...

Looking at vmstat -m a bit further, the top of the report has:

Memory statistics by bucket size
Size   In Use   Free   Requests  HighWater  Couldfree
   16    13116  28356 2063580697    1280       7822
   32    77734   7002  168084205     640     316065
   64   465006  48402 2804541088     320     637084
  128   100182  60010  591859866     160    1850304
  256   500029  12163 1178322001      80     123078

Now, the only things that are using alot of the '256 Size' memory are:

      FFS node494513123629K 127870K204800K401104542    0     0  256
      vfscache449709 29178K  32434K204800K737673766    0     0  64,128,256,512K

Since only 500029 are 'InUse', and since FFS node is exclusively 256 ... 
I'm going to guess that most of vfscache is using something else ... so, 
my question becomes if 123000 'Could be Freed', why aren't they?

Assuming, of course, I'm not on the wrong trail here :(

On Tue, 31 Aug 2004, Marc G. Fournier wrote:

>
> As a follow up, looking at vmstat -m .. specifically the work that David did 
> on seperating the union vs regular vnodes:

Bad ATA Drivers ?

Since updating kernel//ports//src over the past weekend my machine seems to 
error after a period when trying to mount my cdrom or dvd rom drive.  dmesg 
shows the devices where detected on boot but when trying to mount i get the 
following...

mount /cdrom
cd9660: /dev/acd0c: Invalid argument

mount /dvd
cd9660: /dev/acd1c: Input/output error

9:21AM  up 1 day, 13:16, 0 users, load averages: 1.00, 1.02, 1.20

An yes there was a CD & DVD in each drive.

I had this trouble the other day as well and rebooting the machine fixed it, 
so both devices would mount, however since then something has happend so as 
neither will mount.  Any ideas ?
--

-- 
Yours Sincerely
Shinjii
http://virusinfo.rdksupportinc.com
_______________________________________________
freebsd-stable <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe <at> freebsd.org"

This item has been released from quarantine.

This file, which was attached to the message titled "free/flushing vnodes ..." by "scrappy <at> hub.org" and
was quarantined on 8/31/2004 10:43 PM, has been released. 

NOTE: If AutoProtect is enabled, then this restored attachment will be rescanned during the restore. If
the attachment is still infected, the current virus detection policy will apply to this attachment.

_______________________________________________
freebsd-stable <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe <at> freebsd.org"

Re: Bad ATA Drivers ?

* Warren Liddell <shinjii <at> virusinfo.rdksupportinc.com> [2004-09-01 11:12 +1000]:
> Since updating kernel//ports//src over the past weekend my machine seems to 
[...]
> I had this trouble the other day as well and rebooting the machine fixed it, 
> so both devices would mount, however since then something has happend so as 
> neither will mount.  Any ideas ?

Perhaps you have to remake your devices (MAKEDEV)? You didn't tell
which version you ran before, and which you're using now, so nobody
knows wether this would be neccessary.

Tell us your version, and show us the output of ls -l /dev/acd0c /dev/acd1c
if you can't solve it.

Nicolas
_______________________________________________
freebsd-stable <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe <at> freebsd.org"

Re: Bad ATA Drivers ?

> Perhaps you have to remake your devices (MAKEDEV)? You didn't tell
> which version you ran before, and which you're using now, so nobody
> knows wether this would be neccessary.

I fix the problem by detaching ata 1 & re-attaching it which re-enables my DVD 
rom Drive but the cd-rom being on ata0 along with the hdd i cant detach it 
and re-attach it, so that is of some annoyance.

I am using FreeBSD 4.10-STABLE and have been since it became STABLE

>
> Tell us your version, and show us the output of ls -l /dev/acd0c /dev/acd1c
> if you can't solve it.
>
> Nicolas

Problem still exists and is of an annoyance.

crw-r-----  4 root  operator  117,   0 Aug 15 09:34 /dev/acd0c
crw-r-----  4 root  operator  117,   8 Jul  1 14:31 /dev/acd1c

--

-- 
Yours Sincerely
Shinjii
http://virusinfo.rdksupportinc.com
_______________________________________________
freebsd-stable <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe <at> freebsd.org"

Re: vnodes - is there a leak? where are they going?

On Tue, Aug 31, 2004 at 09:21:09PM -0300, Marc G. Fournier wrote:
> 
> I have two servers, both running 4.10 of within a few days (Aug 5 for 
> venus, Aug 7 for neptune) ... both running jail environments ... one with 
> ~60 running, the other with ~80 ... the one with 60 has been running for 
> ~25 days now, and is at the border of running out of vnodes:
> 
> Aug 31 20:58:00 venus root: debug.numvnodes: 519920 - debug.freevnodes: 
> 11058 - debug.vnlru_nowhere: 256463 - vlrup
> Aug 31 20:59:01 venus root: debug.numvnodes: 519920 - debug.freevnodes: 
> 13155 - debug.vnlru_nowhere: 256482 - vlrup
> Aug 31 21:00:03 venus root: debug.numvnodes: 519920 - debug.freevnodes: 
> 13092 - debug.vnlru_nowhere: 256482 - vlruwt
>
> [..]
>
> I've tried shutting down all of the VMs on venus, and umount'd all of the 
> unionfs mounts, as well as the one nfs mount we have ... the above #s are 
> after the VMs (and mounts are recreated ...
> 
> Now, my understanding of the vnodes is that for every file opened, a vnode 
> is created ... in my case, since I'm using unionfs, there are two vnodes 
> per file ... if it possible that there are 'stale' vnodes that aren't 
> being freed up?  Is there some way of 'viewing' the vnode structure?
>
> For instance, fstat shows:
> 
> venus# fstat | wc -l
>    19531

Re: vnodes - is there a leak? where are they going?

On Wed, 1 Sep 2004, Allan Fields wrote:

> On Tue, Aug 31, 2004 at 09:21:09PM -0300, Marc G. Fournier wrote:
>>
>> I have two servers, both running 4.10 of within a few days (Aug 5 for
>> venus, Aug 7 for neptune) ... both running jail environments ... one with
>> ~60 running, the other with ~80 ... the one with 60 has been running for
>> ~25 days now, and is at the border of running out of vnodes:
>>
>> Aug 31 20:58:00 venus root: debug.numvnodes: 519920 - debug.freevnodes:
>> 11058 - debug.vnlru_nowhere: 256463 - vlrup
>> Aug 31 20:59:01 venus root: debug.numvnodes: 519920 - debug.freevnodes:
>> 13155 - debug.vnlru_nowhere: 256482 - vlrup
>> Aug 31 21:00:03 venus root: debug.numvnodes: 519920 - debug.freevnodes:
>> 13092 - debug.vnlru_nowhere: 256482 - vlruwt
>>
>> [..]
>>
>> I've tried shutting down all of the VMs on venus, and umount'd all of the
>> unionfs mounts, as well as the one nfs mount we have ... the above #s are
>> after the VMs (and mounts are recreated ...
>>
>> Now, my understanding of the vnodes is that for every file opened, a vnode
>> is created ... in my case, since I'm using unionfs, there are two vnodes
>> per file ... if it possible that there are 'stale' vnodes that aren't
>> being freed up?  Is there some way of 'viewing' the vnode structure?
>>
>> For instance, fstat shows:
>>
>> venus# fstat | wc -l

Re: 4-stable termios diff behaviour lc/lc_r

On Tue, 31 Aug 2004, Julian Elischer wrote:
>
> this should have been sent to -threads..
> --------------------------------------------
>  >Hi list,
>  >>
>  >> I think I've found a possible bug in 4-stable, though I'm not that
>  >> kind of an expert so I'll leave that decision up to you.
>  >>
>  >> Attached is a little test program that opens /dev/cuaa0 and tries to
>  >> read a couple bytes.
>  >>
>  >> When compiled using "gcc vtime.c -o vtime" there's no problem. For
>  >> example, when you run vtime without anything attached to cuaa0,
>  >> it'll wait about 2 seconds and timeout, since VMIN=0 and VTIME=20.
>  >>
>  >> When compiled using "gcc -pthread vtime.c -o vtime" however, the
>  >> read function returns immediately, which as far as I can understand,
>  >> is not what it's supposed to do.
>  >>
>  >> Does anyone know if this intended or not, or how I can get the right
>  >> behaviour in a threaded program?
>
>
> I've done some more testing. It appears that when linked with lc_r,
> VTIME is completely ignored.

Yes, and it will always be completely ignored.  If you want to
use libc_r on 4.x, you'll have to work around it (use select()
or poll() perhaps).  It is not a problem in 5.x which will be