From owner-freebsd-questions@FreeBSD.ORG Sat Sep 6 08:34:57 2003 Return-Path: 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 E1C2C16A4BF for ; Sat, 6 Sep 2003 08:34:57 -0700 (PDT) Received: from eternal.slumber.org (eternal.slumber.org [68.98.216.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id EFDB443FAF for ; Sat, 6 Sep 2003 08:34:56 -0700 (PDT) (envelope-from flagg@eternal.slumber.org) Received: from eternal.slumber.org (localhost [127.0.0.1]) h86FR7bT001964 for ; Sat, 6 Sep 2003 08:27:07 -0700 Received: (from flagg@localhost) by eternal.slumber.org (8.12.9/8.12.9/Debian-5) id h86FR6ns001962 for freebsd-questions@freebsd.org; Sat, 6 Sep 2003 08:27:06 -0700 Date: Sat, 6 Sep 2003 08:27:06 -0700 From: Shawn Ostapuk To: freebsd-questions@freebsd.org Message-ID: <20030906152706.GB1888@slumber.org> References: <20030906050812.GA835@slumber.org> <3F599B00.9040006@techfak.uni-bielefeld.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3F599B00.9040006@techfak.uni-bielefeld.de> User-Agent: Mutt/1.5.4i Subject: Re: terabyte limit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Sep 2003 15:34:58 -0000 > >with vinum > > > ># newfs /dev/vinum/vinum0 > >/dev/vinum/vinum0: 1085915.5MB (2223954992 sectors) block size 16384, > >fragment size 2048 > > using 5910 cylinder groups of 183.77MB, 11761 blks, 23552 inodes. > >newfs: can't read old UFS1 superblock: read error from block device: > >Invalid arguement > > Try newfs -O 2 /dev/vinum/vinum0 to force ufs2. Hope that works. > Nope, I've tried that and a ton of other options. I've looked into that "can't read old UFS1 superblock error" but its not actually trying to write UFS1, it looks like (someone feel free to correct me if i'm wrong) that its trying to zero out the old UFS1 blocks so older versions of fsck don't mistaken the filesystem for UFS1, try and repair it, and therefore break it. I think it errors out for the same reason, it can't access the drive like the second error. For kick's (like i said i've tried alot of things) i took out that part of the code, planning on just being careful :), and that error went away but i still got the read error from superblock device: Invalid arguement. Someone else commented there should be a "-v", but the option seems to have been removed in 5.1 (5.x?), newfs can figure it out without being told, and does work fine with vinum when its not more than a terabyte. shawn.