Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.cs.su.oz.au!metro!metro!munnari.OZ.AU!news.ecn.uoknor.edu!news.wildstar.net!serv.hinet.net!news.uoregon.edu!vixen.cso.uiuc.edu!howland.reston.ans.net!blackbush.xlink.net!zib-berlin.de!news.tu-chemnitz.de!irz401!uriah.heep!news
From: j@uriah.heep.sax.de (J Wunsch)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: disklabel
Date: 4 May 1996 20:49:43 GMT
Organization: Private BSD site, Dresden
Lines: 46
Message-ID: <4mgft7$mkb@uriah.heep.sax.de>
References: <Pine.SUN.3.90.960502151447.1568B-100000@sandstorm.cs.odu.edu>
Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch)
NNTP-Posting-Host: localhost.heep.sax.de
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Newsreader: knews 0.9.6
X-Phone: +49-351-2012 669
X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E
Jamie Bowden <bowden@cs.odu.edu> wrote:
> I redid one of the drives on my news server the other night, and am
> wondering how important is the label.
Quite more important than the fdisk table. :) You can run BSD fine
without a valid fdisk table, but not without a valid disklabel.
> 8 partitions:
> # size offset fstype [fsize bsize bps/cpg]
> a: 614400 0 4.2BSD 0 0 0 # (Cyl. 0 -
> 614399)
> c: 8410200 0 unused 0 0 # (Cyl. 0 -
> 8410199)
> e: 7795800 614400 4.2BSD 0 0 0 # (Cyl. 614400 -
> 8410199)
> 3:18pm tyger /home/jamie %
>
>
> 3:18pm tyger /home/jamie %df -k
> Filesystem 1K-blocks Used Avail Capacity Mounted on
> /dev/sd0a 201310 102002 83202 55% /
> /dev/sd0s1e 1512670 703310 688346 51% /usr
> /dev/sd1s1e 3278331 1327882 1688182 44% /var/news
> /dev/sd0s1f 2425870 1023984 1207816 46% /var/news/alt/binaries
> procfs 4 4 0 100% /proc
> 3:20pm tyger /home/jamie %
>
> The machine is running fine, but the label doesn't show the last slices
^^^^^^
> correctly. I am wondering if I should be worried.
partitions. Slices are what you can find in the fdisk tables,
partitions are what you can find in the disk label.
Your disk is botched. If you've still got the old figures handy, you
will be able to fix it. The disklabel keeps the resident information
about the BSD-internal (as opposed to outside BSD [fdisk]) disk
layout.
--
cheers, J"org
joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)