Hi
cache_enter() used to panic when cnp-cn_namelen NCHNAMLEN. filesystem
had to check that condition prior cache_enter() call. puffs failed to do
so and therefore had a bug.
In -current, the cnp-cn_namelen NCHNAMLEN has just been pushed into
cache_enter() and the filsystem-based checks
Also that code seems to be able to return values 2^32 although the disklabel
itself cannot store them.
Unfortunately, despite my personal Unix and NetBSD guru saying so, it seems
not to be true.
First, using the ``full disk'' devices as RAIDframe components doesn't work,
the component size
In article julcud$9sd$1...@serpens.de,
Michael van Elst mlel...@serpens.de wrote:
Let wd1 disappear and the raid will try to use wd0a (dk0) and sd0a (dk1).
Of course raidframe will notice the mismatch in this case, but you can
easily imagine more complex scenarios where it doesn't. But a simple
Let wd1 disappear and the raid will try to use wd0a (dk0) and sd0a
(dk1).
This is one reason to use autoconfigured RAIDs when you can. They are
far more immune (completely immune, in my experience) to confusion from
disks attaching in new orders or at new places.
/~\ The ASCII
disklabel has a 2TB limit. that's true on all netbsd platforms.
to partition disks (real or otherwise) greater than 2TB you'll need
to use gpt(8) style partitions.
.mrg.
disklabel has a 2TB limit. that's true on all netbsd platforms.
I know.
to partition disks (real or otherwise) greater than 2TB you'll need
to use gpt(8) style partitions.
I know.
I don't have a disklabel on the components. I do have GPTs on them.
I don't have a disklabel on the RAID set.
e...@math.uni-bonn.de (Edgar =?iso-8859-1?B?RnXf?=) writes:
First, using the ``full disk'' devices as RAIDframe components doesn't work,
the component size is truncated to the modulo-2^32 size.
That's because full disk is just a partition in the disklabel that
spans the full disk as much as
mo...@rodents-montreal.org (Mouse) writes:
This is one reason to use autoconfigured RAIDs when you can. They are
far more immune (completely immune, in my experience) to confusion from
disks attaching in new orders or at new places.
True, but raid autoconfig is only done at boot time.
--
--
First, using the ``full disk'' devices as RAIDframe components
doesn't work, the component size is truncated to the modulo-2^32
size.
That's because full disk is just a partition in the disklabel that
spans the full disk as much as disklabel is capable.
Perhaps are far as the get size
This is one reason to use autoconfigured RAIDs when you can. They
are far more immune (completely immune, in my experience) to
confusion from disks attaching in new orders or at new places.
True, but raid autoconfig is only done at boot time.
Also true. Perhaps there should be some kind of
mo...@rodents-montreal.org (Mouse) writes:
Perhaps are far as the get size interface raidframe uses is
concerned. But it's not _just_ that; see my note upthread about how
the disk drivers treat RAW_PART. And _nothing_ can be just a
partition in the disklabel when there isn't any disklabel.
I'm
11 matches
Mail list logo
