freebsd-hackers Digest, Vol 367, Issue 1
freebsd-hac...@freebsd.org
freebsd...@freebsd.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
or, via email, send a message with subject or body 'help' to
freebsd-hac...@freebsd.org
You can reach the person managing the list at
freebsd-ha...@freebsd.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of freebsd-hackers digest..."
Today's Topics:
1. Re: leak of the vnodes (Mikolaj Golub)
----------------------------------------------------------------------
Message: 1
Date: Sun, 04 Apr 2010 15:26:43 +0300
From: Mikolaj Golub <to.my....@gmail.com>
Subject: Re: leak of the vnodes
To: Kostik Belousov <kost...@gmail.com>
Cc: freebsd...@freebsd.org, Petr Salinger
<Petr.S...@seznam.cz>
Message-ID: <86ljd3m...@kopusha.onet>
Content-Type: text/plain; charset=us-ascii
On Sat, 3 Apr 2010 19:52:38 +0300 Kostik Belousov wrote:
> Then, after you determined the problematic mp, reboot the machine,
> redo the procedure causing leak. From ddb prompt, you can do "show mount",
> find the mp, then do "show mount <mp address>". The later command shall
> produce really large output, listing all mp vnodes, so serial console
> or firewire can be useful. Put output somewhere.
Or use ddb capture buffer :-). In ddb:
capture on
<some commands ...>
capture off
continue
And then
ddb capture print > capture.out
Make sure your capture buffer is large enough (I have in my /etc/sysctl.conf
debug.ddb.capture.bufsize=5242880).
--
Mikolaj Golub
------------------------------
End of freebsd-hackers Digest, Vol 367, Issue 1
***********************************************