Date: Sun, 04 Apr 2010 15:26:43 +0300 From: Mikolaj Golub <to.my.trociny@gmail.com> To: Kostik Belousov <kostikbel@gmail.com> Cc: freebsd-hackers@freebsd.org, Petr Salinger <Petr.Salinger@seznam.cz> Subject: Re: leak of the vnodes Message-ID: <86ljd3mmik.fsf@kopusha.onet> In-Reply-To: <20100403165238.GO2415@deviant.kiev.zoral.com.ua> (Kostik Belousov's message of "Sat\, 3 Apr 2010 19\:52\:38 %2B0300") References: <Pine.LNX.4.62.1004021934550.15800@sci.felk.cvut.cz> <20100402190239.GL2415@deviant.kiev.zoral.com.ua> <Pine.LNX.4.62.1004022337010.16354@sci.felk.cvut.cz> <Pine.LNX.4.62.1004030915440.17349@sci.felk.cvut.cz> <20100403165238.GO2415@deviant.kiev.zoral.com.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86ljd3mmik.fsf>