Date: Fri, 1 May 2009 22:39:45 +0100 From: xorquewasp@googlemail.com To: Alexander Kabaev <kabaev@gmail.com> Cc: freebsd-hackers@freebsd.org Subject: Re: vfs_cache panic, 7.2-prerelease (stable) Message-ID: <20090501213945.GA87334@logik.internal.network> In-Reply-To: <20090501155038.692eb891@kan.dnsalias.net> References: <20090501130536.GA95601@logik.internal.network> <20090501151308.5c9109da@kan.dnsalias.net> <20090501192113.GA15572@logik.internal.network> <20090501155038.692eb891@kan.dnsalias.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2009-05-01 15:50:38, Alexander Kabaev wrote: > On Fri, 1 May 2009 20:21:13 +0100 > xorquewasp@googlemail.com wrote: > > > Hello. > > > > Checking back through my sent mail from the DRI thread, this version > > of -STABLE was checked out and compiled on Fri, 10 Apr 2009 16:42:51 > > +0100. > > > > The machine was so new that I hadn't even set the clock, so the kernel > > timestamps appear to be Jan 1. > > > > I'll make an attempt to check out today's -STABLE and compile it but > > I'm not optimistic that the machine will actually be able to build > > world without reverting to a release first. > > You can always try to bypass namecache altogether while you are > building the new kernel: do sysctl debug.vfscache=0 Hi. Updating to today's -STABLE appears to have fixed the problem (or at least it doesn't occur for the usage described in the PR!). Thanks! xw
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090501213945.GA87334>