Re: raid1: unable to open device, error = 16

[buhrow%lothlorien.nfbcal.org@localhost (Brian Buhrow)]

        hello.  that's what I rand into as well.  I found that using the full
pathname to the raid.conf file with raidctl caused things to work as
expected.  Doing less caused confusion if I didn't happen to be in the
right working directory.
-Brian

`i

On Jul 25,  7:34pm, Edgar =?iso-8859-1?B?RnXf?= wrote:
} Subject: Re: raid1: unable to open device, error = 16
} > OK, it's reproducible. After newfs dk5, gpt show raid1 doesn't work any 
more.
} Another reboot, and it worked again.
} 
} The problem seems not to be newfs (or not only), but raidctl.
} 
} If I'm inside /dev and raidctl -c /etc/raid1.conf raid1, I get that "unable 
} to open device, error = 16". If I do raidctl -c /etc/raid1.conf raid1 outside 
} /dev, it works. If I do raidctl -c /etc/raid1.conf rraid1 (note the "r") 
} inside /dev, it also works.
} 
} So it's probably not as bad as I initially thought, but confusing enough.
>-- End of excerpt from Edgar =?iso-8859-1?B?RnXf?=