Date: Wed, 22 Dec 2004 16:59:18 +0000 From: Peter Risdon <peter@circlesquared.com> To: Marco Beishuizen <marco@beishuizen.info> Cc: FreeBSD questions mailing list <questions@freebsd.org> Subject: Re: fsck locks up SMP system (5.3-REL) Message-ID: <41C9A7E6.3090701@circlesquared.com> In-Reply-To: <Pine.BSF.4.61.0412221538030.249@tsunami.bsd> References: <Pine.BSF.4.61.0412221248290.249@tsunami.bsd> <41C974EF.8020002@uni-mainz.de> <Pine.BSF.4.61.0412221435380.249@tsunami.bsd> <41C97F72.4030409@uni-mainz.de> <Pine.BSF.4.61.0412221538030.249@tsunami.bsd>
next in thread | previous in thread | raw e-mail | index | archive | help
Marco Beishuizen wrote: > On stardate Wed, 22 Dec 2004, the wise O. Hartmann entered: > >> Dear Marco. >> Thanks. In my case, FreeBSD 5.3 dies in single user mode on nearly >> each disk activity (it is obviously a FreeBSD 5.3-issue with >> my ASUS CUR-DLS based system). >> >> Please take a look at fsck_ffs(8) man page. There is at the end of the >> description of the options an explanation of the lost+find facility. >> Obviously orphaned files and directories (and in most cases those >> which are expected to be some of them) are gathered and reconnected in >> lost+found. My 'periodic' cron-job deletes the contents of lost+found >> every 7 days. >> Oliver > > > Well the problem didn't dissappear. I was just checking the filesystem > with the midnight commander, and suddenly mc froze in "ufs"-state. Now > I'm running fsck again. > What's being logged? Lots of dma errors in /var/log/messages? Peter.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?41C9A7E6.3090701>