Date: Fri, 9 May 2003 07:40:25 +0100 From: David Malone <dwmalone@maths.tcd.ie> To: freebsd-hackers@freebsd.org Subject: Re: cache_purge > cache_zap segmentation fault Message-ID: <20030509064025.GA91122@walton.maths.tcd.ie> In-Reply-To: <20030508195410.A670@internetDog.org> References: <20030508150341.B28906@internetDog.org> <1789.1052421172@critter.freebsd.dk> <20030508195410.A670@internetDog.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, May 08, 2003 at 07:54:10PM -0400, Ali Bahar wrote: > Considering its increasing frequency, I even suspected that the > filesystem had been corrupted -- in a way undetected by fsck. But, a > 'normal' filesystem corruption exhibits _random_ crashes, not ones > consistently following the above execution thread. To me it seems very unlikely that a corrupted filesystem would result in a corrupted name cache. The name cache is independendent of the filesystem and is only populated as lookups in the filesystem code complete. If there were a problem it seems more likely that either fsck, the filesystem code or dirhash would catch the problem. Mind you, I couldn't say for certain that some subtle corruption might not cause the problem. Is it possible that one of your modules is somehow stomping on memory that doesn't belong to it? David.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030509064025.GA91122>