*BSD News Article 8780


Return to BSD News archive

Newsgroups: comp.unix.bsd
Path: sserve!manuel.anu.edu.au!munnari.oz.au!news.hawaii.edu!ames!sun-barr!cs.utexas.edu!uunet!news.univie.ac.at!news.tu-graz.ac.at!fstgds01!chmr
From: chmr@fstgds01.tu-graz.ac.at (Christoph Robitschko)
Subject: Re: [386BSD] Disklabel help and large drives (1.7 gig)
Message-ID: <1992Dec11.180246.17228@news.tu-graz.ac.at>
Sender: news@news.tu-graz.ac.at (USENET News System)
Nntp-Posting-Host: fstgds01
Organization: Technical University of Graz, Austria
References: <1992Dec10.171917.20431@decuac.dec.com>
Date: Fri, 11 Dec 92 18:02:46 GMT
Lines: 27

In article <1992Dec10.171917.20431@decuac.dec.com> darryl@sai.com writes:
>
>I know this is a FAQ which I have read, but I can't seem to partition
>my disk to anything but the default.  What am I doing wrong?   Do
>I need a disktab entrie to match my disk, before disklabel will work?
>Does the partition relate to fdisk format?
>
I had this problem, too. The error message was something like 'partition
c extends past end of drive'. I simply gave disklabel a bigger number
of cilynders than is actually on drive, that cured the problem.
I think disklabel verifies that nsectors*ntracks*ncylinders >= nblocks,
which is wrong for some drives.
No, you don't need a disktab entry.
No, the disklabel has nothing to do with fdisk.
>
>Also does 386BSD have any problem supporting drives larger than 1 gig?
>
It seems so. I tried yesterday to hook up a 2 Gig disk and make a
filesystem on a 1.9 Gig partition. When I then mounted the partition
and copied some files over (dump | restore), it destroyed the file
system (root directory inode was mangled). The other partition was not
affected, so I guess there was some wraparound inside the partition.
This was with the Seagate ST01 SCSI driver.

							Christoph
-- 
..signature: No such file or directory