On Fri, Nov 25, 2005 at 04:50:34PM +0100, mickey wrote:
> default 'c' type is unused.
> at least on default systems...
On REAL disks, yes. On ccd disks, it seems to be different. Or maybe
ccdconfig screws it up.
> > 2. The OpenBSD slices of my disks start at sector 24659775. This is also
> > where the a partition of these disks start. It isn't that way because I
> > made it that way, it was set up that way by the initial label editor
> > when I did the installation.
>
> some pplz use 'c' for their ccd components -- WRONG!
Pardon my rudeness, but are you sure? It works fine for me. Other people
have reported it works fine for them. I don't know any implementation
details, but maybe you do: what actually goes wrong when you use the c
partition on a ccd device?
> > 3. From 2, I conclude that wherever the BSD disklabel is stored, this
> > does not affect where my partitions can be. The disklabel could be
> > stored in my root partition, for all I know.
>
> disklabel is the sector #1 of the fdisk partition
The fdisk partition that is the OpenBSD slice? Because my a partition
starts at the exact same sector as that slice, and there seem not to be
any problems. Again, this is how the system set it up for me, I didn't
change the start position of my a partition. Maybe ffs can accomodate
disk labels and there isn't any problem?
> > 4. I have a ccd device starting at sector 41110398, with a size of
> > 32901057 sectors. Inside the ccd device is a c partition of 32901056
> > sectors, starting at sector 0, with type 4.2BSD. This isn't because I
> > set it up this way, this is how the device was set up when I first ran
> > disklabel. I never changed anything there.
>
> oh uhm must be a bug in disklabel spoofing (:
You mean that it's actually unused, but some spoofing code reports it to
disklabel as 4.2BSD? I don't think so. If you change the type from
4.2BSD to unused, you can partition as normal. Make your a partition,
and all that. And disklabel will report it as unused afterwards. By all
appearances, it looks like it _really_ does get set to 4.2BSD.
> it's not about how the 'c' is setup.
> you can screw it on normal drive as well.
> just run a newfs on it!
I see how you can screw it up on a real drive, especially one that has
fdisk partitions. Can't have an fdisk partition and an ffs filesystem in
the same sector. About disklabel, I don't know. What I'm seeing (my a
partition starting on the same sector as my OpenBSD slice) suggests
that, perhaps, they can coexist.
> the point is that the ccd part must be started w/ an offset as well!
Well, there is that one missing sector. Maybe the ccd driver
automatically reserves space for the label? I'm just making wild
guesses, trying to explain why it works for me, even though you say it
shouldn't.
To recap, I would very much like to see the following questions answered
beyond all doubt:
1. Is it or is it not wrong to use the 4.2BSD c partition that gets
created for you?
2. If it is wrong, why does it get created?
So far, there is you answering question 1 with a definite "it's wrong",
and me answering with an "it's not wrong", backed up with the evidence
that it works for me without any problems.
I hope I'm not being too annoying about this. It's just that I wrote the
HOWTO to clarify things and makes sense of the scattered and
inconsistent information on ccd and mirroring. I have little desire to
incorporate any information in it before I am very sure it is correct. I
want to clear up the confusion, not add to it.
Cheers,
Bob
---
The more you learn about Windows, the more you are amazed it works at all
-- Pfhreakaz0id on Slashdot
[demime 1.01d removed an attachment of type application/pgp-signature]
