On Wed, 16 Oct 2002, walt wrote:
> Bruce Evans wrote:
> > On Wed, 16 Oct 2002, walt wrote:
> >
> >>Bruce Evans wrote:
> >>
> >>
> >>>Don't use extended partitions directly. It is easy to
> >>>make a mess by clobbering the pointers to the logical drive
> >>>within them.
>
> >>I need to ask for clarification on this point. What do you
> >>mean by 'directly'?
>
> > Just write to them using anything that doesn't understand that they
> > are containers for logical drives. E.g., newfs would leave their
>
> Once again you leave me puzzled. 'newfs /dev/ad2s8' is exactly how
> I formatted the partition and everything is working perfectly.
/dev/ad2s8 isn't an extended partition. It is a logical drive within
an extended partition. In FreeBSD, only primary extended partitions
are exposed as devices. You probably have a layout something like:
ad2s4: extended partition
ad2s5: logical drive within ad2s4
[ad2s4X]: nameless extended partition within ad2s4
ad2s6: logical drive within ad2s4X
[ad2s4XX]: nameless extended partition within ad2s4X
ad2s7: logical drive within ad2s4XX
[ad2s4XXX]: nameless extended partition within ad2s4XX
ad2s8: logical drive within ad2s4XXX
> In addition I see this on -CURRENT (with GEOM):
> #disklabel ad2s8
> disklabel: ioctl DIOCGDINFO: Operation not supported by device
>
> and this on -STABLE (different machine):
> # disklabel ad0s7
> disklabel: ioctl DIOCGDINFO: Invalid argument
>
> so (for me) disklabel does not work on extended/logical partitions.
This behaviour is the same as for all slices except the whole disk
slice. There is no label on them until you write one.
Bruce
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
