Date: Thu, 20 Mar 2003 15:25:31 -0500 (EST) From: Jeff Roberson <jroberson@chesapeake.net> To: "Evgueni V. Gavrilov" <aquatique@rusunix.org> Cc: Kirk McKusick <mckusick@beastie.mckusick.com>, Poul-Henning Kamp <phk@phk.freebsd.dk>, <dwmalone@FreeBSD.org>, Mike Makonnen <mtm@identd.net>, <src-committers@FreeBSD.org>, <cvs-src@FreeBSD.org>, <cvs-all@FreeBSD.org> Subject: Re: kern/42277 Message-ID: <20030320152458.M66343-100000@mail.chesapeake.net> In-Reply-To: <3E798894.4060603@rusunix.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 20 Mar 2003, Evgueni V. Gavrilov wrote: > Evgueni V. Gavrilov wrote: > > >> Have you tried aggressively setting the word @64 to random values ? > >> With a little luck this will make some code somewhere unhappy and > >> you might get a hint who's responsible ? > > well, really overbold idea :-) > > I'll try it right now. > well, I followed this advise and after defining trashed memory I set unused field to 0xffffffff. > I've been waiting for the hit more than 2 adys, but haven't got it. :-( > > But I've just received this console messages: > Mar 20 15:10:35 <kern.crit> rshb /kernel: bad block -65536, ino 21699 > Mar 20 15:10:35 <kern.err> rshb /kernel: pid 6 (syncer), uid 66 on /var: bad block > Mar 20 15:10:35 <kern.crit> rshb /kernel: handle_workitem_freeblocks: block count > > block number (-65536) looks like invalid. > find /var -inum 21699 found file /var/lock/browse.dat (this file got corrupted). > > Any luck with recording the malloc_type of the previous owner? This will tell you who is most likely to have written to the memory. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-src" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030320152458.M66343-100000>