From owner-freebsd-hackers Sun Nov 10 1:31:33 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 5BC8F37B401 for ; Sun, 10 Nov 2002 01:31:32 -0800 (PST) Received: from skywalker.rogness.net (skywalker.rogness.net [64.251.173.102]) by mx1.FreeBSD.org (Postfix) with ESMTP id A0CAF43E4A for ; Sun, 10 Nov 2002 01:31:31 -0800 (PST) (envelope-from nick@rogness.net) Received: from skywalker.rogness.net (localhost [127.0.0.1]) by skywalker.rogness.net (8.12.5/8.12.5) with ESMTP id gAA9Y70H075328; Sun, 10 Nov 2002 02:34:07 -0700 (MST) (envelope-from nick@rogness.net) Received: from localhost (nick@localhost) by skywalker.rogness.net (8.12.5/8.12.5/Submit) with ESMTP id gAA9Y07Q075325; Sun, 10 Nov 2002 02:34:06 -0700 (MST) X-Authentication-Warning: skywalker.rogness.net: nick owned process doing -bs Date: Sun, 10 Nov 2002 02:33:55 -0700 (MST) From: Nick Rogness To: Poul-Henning Kamp Cc: Larry Sica , Subject: Re: Filesystem corruption In-Reply-To: <45812.1036861207@critter.freebsd.dk> Message-ID: <20021110022411.N75268-100000@skywalker.rogness.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 On Sat, 9 Nov 2002, Poul-Henning Kamp wrote: > 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. I've been running dump for years on live filesystems with FreeBSD and never had a problem. I was not aware of any snapshot feature available for 4.X-STABLE (only 5.0)? umounting a live filesystem to back it up is not a solution. What should I be using to backup a live filesystem? Nick Rogness - "Wouldn't it be great if we could answer people with a kick to the crotch?" -maddox@xmission.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message