[no subject]

D543.4050506@fs.ei.tum.de> <200707162126.l6GLQcsM027869@apollo.backplane.com> <469BE4E1.1030705@fs.ei.tum.de>
From: Matthew Dillon <dillon@apollo.backplane.com>
Subject: Re: [issue730] Latest DEVEL still reflects old pkg_* paths
Date: Mon, 16 Jul 2007 14:50:44 -0700 (PDT)
BestServHost: crater.dragonflybsd.org
List-Post: <mailto:bugs@crater.dragonflybsd.org>
List-Subscribe: <mailto:bugs-request@crater.dragonflybsd.org?body=subscribe>
List-Unsubscribe: <mailto:bugs-request@crater.dragonflybsd.org?body=unsubscribe>
List-Help: <mailto:bugs-request@crater.dragonflybsd.org?body=help>
List-Owner: <mailto:owner-bugs@crater.dragonflybsd.org>
Sender: bugs-errors@crater.dragonflybsd.org
Errors-To: bugs-errors@crater.dragonflybsd.org
Lines: 22
NNTP-Posting-Host: 216.240.41.25
X-Trace: 1184622781 crater_reader.dragonflybsd.org 796 216.240.41.25
Xref: crater_reader.dragonflybsd.org dragonfly.bugs:7388


:I don't think vinum ever writes to the label area.  You are not supposed to start your partition on sector 0.

    Unfortunately it does if you happen to start your partition at sector 0.
    It writes to offset 4096 and the label area is the first 8K of the disk.
    Even worse, the auto-start code seems to completely ignore the
    partitioning scheme on the disk.

:what's wrong with vinum right now?  I always had to pass all drives or it wouldn't work.
:
:cheers
:  simon

    There's something going when you 'vinum start' and 'vinum stop'.  Do
    it a few times and the kernel blows up.  Literally.

    Maybe it doesn't happen when it does the automatic scan at boot time
    when using a vinum root.  It definitely occurs when I do it manually.

					-Matt
					Matthew Dillon 
					<dillon@backplane.com>