From owner-freebsd-questions Thu Mar 6 6:57:10 2003 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BFCA337B401 for ; Thu, 6 Mar 2003 06:57:08 -0800 (PST) Received: from mired.org (ip68-97-54-220.ok.ok.cox.net [68.97.54.220]) by mx1.FreeBSD.org (Postfix) with SMTP id A259643F85 for ; Thu, 6 Mar 2003 06:57:07 -0800 (PST) (envelope-from mwm-dated-1047394626.aaa80a@mired.org) Received: (qmail 59631 invoked from network); 6 Mar 2003 14:57:06 -0000 Received: from localhost.mired.org (HELO guru.mired.org) (127.0.0.1) by localhost.mired.org with SMTP; 6 Mar 2003 14:57:06 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15975.25025.373837.32139@guru.mired.org> Date: Thu, 6 Mar 2003 08:57:05 -0600 To: joe mcguckin Cc: Subject: Re: DUMP errors FreeBSD 4.7-RC In-Reply-To: References: X-Mailer: VM 7.07 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`; h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ From: Mike Meyer X-Delivery-Agent: TMDA/0.70 (Pensive) Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In , joe mcguckin typed: > While dumping a 75G partition, I receive the following errors: > DUMP: 21.52% done, finished in 0:51 > DUMP: read error from /dev/ad2s1: Invalid argument: [block -622926708]: > count=7168 > /var/log/messages: > Mar 5 19:15:20 mail /kernel: dscheck(#ad/0x20012): negative b_blkno > -622926708 > > What does this mean? Is there a known problem with dump? My first reaction is that there's something wrong with your disk drive or file system. The system is trying to do disk I/O to a negative block number on the drive, which simply doesn't exist. On second thought, it may be a bug somewhere in the system - not necessarily dump. Try fsck'ing the file system in r/o mode to see if you have a problem on it. If that's okay, can you try doing a recursive copy of the file system to /dev/null to see if the error shows up there as well? http://www.mired.org/consulting.html Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message