On Fri, Oct 19, 2001 at 08:24:57AM -0700, John Baldwin wrote:
> On 19-Oct-01 Chad David wrote:
> > I posted a bug report and patch in kern/29104 and Dima Dorfman also mentioned
> > this in July/August, but it still has not been resolved.  The method of
> > triggering it that I detailed in my bug report no longer seems to work,
> > but I've managed to create another one.
> > 
> ># mdconfig -a -t swap -s 32m -u 10
> ># disklabel -r -w md10 auto
> ># disklabel -e md10e (copy c to e and set type to 4.2BSD)
> ># ls -l /dev/md10*
> > crw-r-----  1 root  operator   95, 0x00010052 Oct 19 01:50 /dev/md10
> > crw-r-----  1 root  operator   95,  82 Oct 19 02:00 /dev/md10c
> > crw-r-----  1 root  operator   95,  84 Oct 19 01:55 /dev/md10ec
> > crw-------  1 root  wheel      95, 0xffff00ff Oct 19 01:50 /dev/mdctl
> Well, you are supposed to be running disklabel -e on md10, not md10e.  You edit
> the disklabel on a disk or slice, not the disklabel from inside of a partition
> defined by that disklabel.  Make sense? :)  Disklabel should probably fail to
> actually run in this case since md10e doesn't exist and certainly wouldn't have
> a valid disklabel to edit if it did exist.

        Yes, that does make sense.  Thank you.  In normal cases disklabel would
        have failed, but the (md) disk clone code seems to (incorrectly) create
        it on the fly.  Even an ls /dev/md10e would create the file.  The problem
        is that ls -l md10eeec returns

        crw-r----- 1 root operator 95, 20 Oct 19 02:19 /dev/md2eeec
        which I'm guessing is a bad device name :).

        Since phk has indicated where the real problem is I will see if I can
        track it down and provide a patch.


Chad David        [EMAIL PROTECTED]
ACNS Inc.         Calgary, Alberta Canada
"When Linux was first ported to the Furby platform,
it suffered from significant stability and performance
problems, which gave the Furby an unfortunate reputation
as being unsuitable for enterprise-level computing."
                                 -- furbeowulf site

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to