Date: Wed, 4 Oct 2006 17:08:08 +0300 From: Kostik Belousov <kostikbel@gmail.com> To: Vivek Khera <vivek@khera.org> Cc: stable@freebsd.org Subject: Re: ffs snapshot lockup Message-ID: <20061004140808.GD89654@deviant.kiev.zoral.com.ua> In-Reply-To: <DFEA4E5F-2337-4383-8765-F5901BDA49E9@khera.org> References: <917B087C-5E13-4D7F-94FA-95CB0E5C1884@khera.org> <20060922190328.GA64849@xor.obsecurity.org> <555B84D2-520F-44D6-84D6-CF9CE7EE47C7@khera.org> <20060922203654.GA65693@xor.obsecurity.org> <847DD3A5-D5DD-4D3E-B755-64B13D1DA506@khera.org> <20061003084315.GA89654@deviant.kiev.zoral.com.ua> <DFEA4E5F-2337-4383-8765-F5901BDA49E9@khera.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--EP0wieDxd4TSJjHq Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Oct 04, 2006 at 09:56:54AM -0400, Vivek Khera wrote: >=20 > On Oct 3, 2006, at 4:43 AM, Kostik Belousov wrote: >=20 > >>Details are posted at http://vivek.khera.org/scratch/crashlogs/ > >> > >>I have the crashdumps available to a kernel hacker upon request (i'd > >>rather not make them generally available to the public...) > >> > >It seems that you have snapshotted fs exported by nfsd ? At least, =20 > >18a is > >definitely the case. I have the patch (for current) that shall fix =20 > >the issue. > >In fact, you need two patches: > > >=20 > So last night I patched my 6.2-PRE and installed the kernel and =20 > rebooted. At 03:09 I got paged that the server was not responding. It =20 > had dropped into the kernel debugger on the console again. Typescript =20 > 19 (posted at the above URL) is the output of the debugging commands =20 > for it. These patches did not solve my problem (or maybe I have =20 > multiple problems and they only solved one.) >=20 > The only thing I think was running at the time would be a large file =20 > copy from a remote system to this one using rsync. As I understand, you got the panic. Then, you shall post the panic message. If you have core file, then running kgdb on the core may show required information. (it shall be on the console exactly before en and backtrace (using the bt command of ddb) of the paniced thread. --EP0wieDxd4TSJjHq Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFI8BHC3+MBN1Mb4gRAsBuAJ96qkoiUD6q+tFFgUweWc+CVHs+5QCgjpZI 9veDZLSBUOuUgd2Or2c6PSM= =a2jT -----END PGP SIGNATURE----- --EP0wieDxd4TSJjHq--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061004140808.GD89654>