From owner-freebsd-stable@FreeBSD.ORG Thu Jul 1 02:12:06 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 57AD216A4CE for ; Thu, 1 Jul 2004 02:12:06 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0D23F43D2D for ; Thu, 1 Jul 2004 02:12:06 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id E18E172DF4; Wed, 30 Jun 2004 19:12:01 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id DF95272DF2; Wed, 30 Jun 2004 19:12:01 -0700 (PDT) Date: Wed, 30 Jun 2004 19:12:01 -0700 (PDT) From: Doug White To: Vladimir Zhurov In-Reply-To: <40E31C35.9020307@uwo.ca> Message-ID: <20040630190707.T66769@carver.gumbysoft.com> References: <40DEDCD2.3020606@uwo.ca> <20040628172309.D43333@carver.gumbysoft.com> <40E31C35.9020307@uwo.ca> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-stable@freebsd.org Subject: Re: dscheck(#ar/2): negative b_blkno error on FreeBSD-4.10-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jul 2004 02:12:06 -0000 On Wed, 30 Jun 2004, Vladimir Zhurov wrote: > Thank you for reply. > > As file system problems started to pile up I have decided to re-format > and restore from backups. I have tested all four HDD's in array using WD > diagnostic utility and extended test did not find any problems. > So I attempted to re-initialize array using the following method from > the handbook (section 13.3.2.2 from "Adding disks" section (with > modifications at newfs stage)): > > # dd if=/dev/zero of=/dev/ar0 count=2 > # disklabel /dev/ar0 | disklabel -BrR ar0 /dev/stdin > # newfs -U /dev/ar0c Some problems: 1. You forgot to create the array. 2. This is a 'dangerously dedicated' partition and should not be used for booting. Run fdisk(8) and create a slice first, then disklabel that. 2. Don't use partition c, its magic. Run disklabel -e on ar0 after the previous diskalbel command and use a different partition. You can copy the parameters for partition c, to, say, d, but don't use c directly. > However, if I would run fsck /dev/ar0c it would immediately report > hundreds of partially allocated inodes. This usually happens if only part othe array is being written to but the entire array is being read from. If you were to mount the partition, you'd get a panic. > > fdisk ar0 reports the following: > > ******* Working on device /dev/ar0 ******* > parameters extracted from in-core disklabel are: > cylinders=19452 heads=255 sectors/track=63 (16065 blks/cyl) > > Figures below won't work with BIOS for partitions not in cyl 1 > parameters to be used for BIOS calculations are: > cylinders=19452 heads=255 sectors/track=63 (16065 blks/cyl) > > Media sector size is 512 > Warning: BIOS sector numbering starts with sector 1 > Information from DOS bootblock is: > The data for partition 1 is: > > The data for partition 2 is: > > The data for partition 3 is: > > The data for partition 4 is: > sysid 165,(FreeBSD/NetBSD/386BSD) > start 0, size 50000 (24 Meg), flag 80 (active) > beg: cyl 0/ head 0/ sector 1; > end: cyl 1023/ head 255/ sector 63 > > Is it controller/cable/some other hardware problem or is it software > related and I am just doing something wrong? > > Vlad. > > >>dmesg.today: > >>dscheck(#ar/2): negative b_blkno -1721888480 > >> > >>messages: > >>/kernel: dscheck(#ar/2): negative b_blkno -1721888480 > > > > > > I've seen this if the array or partition table is corrupted. The check is > > at the front of dscheck() in src/sys/kern/subr_diskslice.c. You might > > make sure your raid array is functioning normally and the fdisk table > > hasn't been spammed. > > > > > >>Does anyone know what is the reason for such error and whether it is > >>critical? > > > > > > It shouldn't happen -- you might go exploring with fdisk(8). > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org