Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 21 Oct 1998 18:00:32 +0930
From:      Greg Lehey <grog@lemis.com>
To:        Bruce Albrecht <bruce@zuhause.mn.org>, Jaime Bozza <wheelman@nuc.net>
Cc:        current@FreeBSD.ORG
Subject:   Subdividing synthetic disks (was: newfs problems, more information:)
Message-ID:  <19981021180032.X21008@freebie.lemis.com>
In-Reply-To: <13869.12610.899877.506387@zuhause.zuhause.mn.org>; from Bruce Albrecht on Tue, Oct 20, 1998 at 07:56:34PM -0500
References:  <13868.3117.390224.376379@zuhause.zuhause.mn.org> <003801bdfc74$da58cae0$313d31cc@electron.nuc.net> <13869.12610.899877.506387@zuhause.zuhause.mn.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday, 20 October 1998 at 19:56:34 -0500, Bruce Albrecht wrote:
> Jaime Bozza writes:
>>> You do it the same way you do it for any other disk.  You create the
>>> partition information, and do a disklabel for ccd0 to write the label,
>>> and then you newfs each partition, ccd0d, ccd0e, ...
>>
>> Are you saying you can have subpartitions within a ccd?  (Which in itself
>> is formed by partitions on the original drives)
>>
>> That could be pretty interesting.  I've fiddled with disklabel and was
>> finally able to create a disklabel for a ccd.  But I haven't been able to
>> create a partition 'e' ... disklabel returns "Bad partition name".  I was
>> able to create an 'a' partition though.
>
> I never had any problem doing so.  Here's my ccd's disklabel entry:
>
> (snip)

Why do you want to do this?  Would you still find a reason to do it
with vinum?

> I've been told that you're better off not using a ccd partition for
> swap,

Right.  The ccd driver malloc()s, and there's the danger of a deadlock
if malloc tries to swap.  I'm working on a solution for vinum, which
currently carries the same danger.

Greg
--
See complete headers for address, home page and phone numbers
finger grog@lemis.com for PGP public key

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19981021180032.X21008>