Date: Thu, 11 Jul 2013 12:54:35 +0200 From: Ian FREISLICH <ianf@clue.co.za> To: John Baldwin <jhb@freebsd.org> Cc: Konstantin Belousov <kostikbel@gmail.com>, freebsd-current@freebsd.org Subject: Re: Filesystem wedges caused by r251446 Message-ID: <E1UxEWB-0000il-21@clue.co.za> In-Reply-To: <201307091202.24493.jhb@freebsd.org> References: <201307091202.24493.jhb@freebsd.org> <20130704082113.GJ91021@kib.kiev.ua> <E1Uudqq-0001ka-E7@clue.co.za> <E1UufRq-0001sg-HG@clue.co.za>
next in thread | previous in thread | raw e-mail | index | archive | help
John Baldwin wrote: > On Thursday, July 04, 2013 5:03:29 am Ian FREISLICH wrote: > > Konstantin Belousov wrote: > > > > > > Care to provide any useful information ? > > > > > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers- > handbook/kerneldebug-deadlocks.html > > > > Well, the system doesn't deadlock it's perfectly useable so long > > as you don't touch the file that's wedged. A lot of the time the > > userland process is unkillable, but often it is killable. How do > > I get from from the PID to where the FS is stuck in the kernel? > > Use kgdb. 'proc <pid>', then 'bt'. So, I setup a remote kbgd session, but I still can't figure out how to get at the information we need. (kgdb) proc 5176 only supported for core file target In the mean time, I'll just force it to make a core dump from ddb. However, I can't reacreate the issue while the mirror (gmirror) is rebuilding, so we'll have to wait for that to finish. Ian -- Ian Freislich
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E1UxEWB-0000il-21>