From owner-freebsd-fs@FreeBSD.ORG Thu Sep 11 07:12:50 2003 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 345C916A4BF for ; Thu, 11 Sep 2003 07:12:50 -0700 (PDT) Received: from eternal.slumber.org (eternal.slumber.org [68.98.216.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id B002D4400F for ; Thu, 11 Sep 2003 07:12:48 -0700 (PDT) (envelope-from flagg@eternal.slumber.org) Received: from eternal.slumber.org (localhost [127.0.0.1]) h8BE5lbT025170; Thu, 11 Sep 2003 07:05:47 -0700 Received: (from flagg@localhost) by eternal.slumber.org (8.12.9/8.12.9/Debian-5) id h8BE5kh7025168; Thu, 11 Sep 2003 07:05:46 -0700 Date: Thu, 11 Sep 2003 07:05:46 -0700 From: Shawn Ostapuk To: Chris Jackman Message-ID: <20030911140546.GE1888@slumber.org> References: <20030910183301.GA17366@slumber.org> <20030911070248.GA69505@collab.or8.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030911070248.GA69505@collab.or8.net> User-Agent: Mutt/1.5.4i cc: freebsd-fs@freebsd.org Subject: Re: terabyte limit problem with vinum/ccd X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Sep 2003 14:12:50 -0000 > I'm just curious about this. > in /usr/src/sbin/newfs/mkfs.c, have you tried > commenting out the if block around line 438 ? > > > * Wipe out old UFS1 superblock(s) if necessary. > */ > if (!Nflag && Oflag != 1) { > i = bread(&disk, SBLOCK_UFS1 / disk.d_bsize, chdummy, SBLOCKSIZE); > if (i == -1) > err(1, "can't read old UFS1 superblock: %s", disk.d_error); > ..... (continues) > > > I have zero knowledge of this code, but I'm still curious if it'd work =). > Actually that's something I already tried, If i take it out it fails with something like "disk write error: invalid arguement" similar to the ccdconfig :) It seems any call to bwrite fails when the drive is larger than 1TB. (which is why -N seems to work with no issues, calls wtfs which doesnt call bwrite when the Nflag is set) -shawn