From owner-freebsd-hackers Sat Nov 9 9: 0:19 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AE69337B401 for ; Sat, 9 Nov 2002 09:00:17 -0800 (PST) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id CD28243E3B for ; Sat, 9 Nov 2002 09:00:16 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.6/8.12.6) with ESMTP id gA9H07Or045813; Sat, 9 Nov 2002 18:00:07 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Larry Sica Cc: Nick Rogness , freebsd-hackers@FreeBSD.ORG Subject: Re: Filesystem corruption In-Reply-To: Your message of "Sat, 09 Nov 2002 11:55:06 EST." Date: Sat, 09 Nov 2002 18:00:07 +0100 Message-ID: <45812.1036861207@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message , Larry Sica wri tes: >-----BEGIN PGP SIGNED MESSAGE----- >Hash: SHA1 > >Not sure if hackers is the correct place to ask about this but... > >On Friday, November 8, 2002, at 06:28 PM, Nick Rogness wrote: > >> >> We have a server that is doing some wierd things. /var/mail filesystem >> (/dev/idad2s1e) is reporting errors during certain tasks (like dump). >> It does fsck clean umounted. I have yet to see this type of error and >> can't tell whether this is a bug or a hardware problem: >> >> Nov 8 15:41:20 pop1 /kernel: dscheck(#idad/0x20014): negative b_blkno >> -791620152 >> Nov 8 15:41:20 pop1 /kernel: dscheck(#idad/0x20014): negative b_blkno > >I've seen mention of this before, not sure what the fix was. I heard >about this a few years ago on some quantam drives, the guy updated his >firmware and it went away iirc. Does it do this only when you dump or >under other circumstances? If other circumstances, which ones? The fix is to not run dump(8) on a live filesystem. You should either use a snapshot or umount the device. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message