On Tue, Nov 04, 2008 at 01:03:37PM -0500, William Boshuck wrote:
> On Tue, Nov 04, 2008 at 12:59:29PM -0500, William Boshuck wrote:
> > On Tue, Nov 04, 2008 at 05:39:46PM +0100, Christophe Rioux wrote:
> > > > On Tue, Nov 04, 2008 at 04:31:57PM +0100, [EMAIL PROTECTED] wrote:
> > > > > I just try to install OpenBSD 4.4 on a serveur (HP DL120
> > > > G5) to test the
> > > > > functionality of the raid (seens it works again .).
> > > > >
> > > > > I configure the first disk without any issue, and then try following
> > > > > commands:
> > > > >
> > > > > disklabel wd0 > disklabel.wd1
> > > > > fdisk -i wd1
> > > > > disklabel -R -r wd1 disklabel.wd1
> > > > > newfs /dev/wd1a
> > > > >
> > > > > Error:
> > > > > newfs: /dev/wd1a: block device
> > > >
> > > > Second section of the newfs(8) manpage.
> > > >
> > > Great ... This worked in 4.3 without any thing else;
> >
> > Likely not just as typed above.
>
> Sorry, this does seem ok in 4.3. (An example in
> the FAQ uses a relative path, and that's what I've
> always done.)
It only seems ok in 4.3 *if you ignore the warning from newfs*.
I repeat: running newfs on a block device is not good. Use the raw device.
4.4 enforces that, but if you are running newfs on an older system,
this holds too.
Background: writing to a block device is not order-preserving: newfs
writes multiple times to the same block. So you can end up with a
filesystem that is inconsitent from the beginning.
-Otto
