[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: partitioning >2TB?
On Thu, Nov 20, 2008 at 03:50:01PM -0500, der Mouse wrote:
> >> disklabel itself is, of course, not suitable because of its 32-bit
> >> limits. So I started looking at wedges, [...]
> > Any reason why you don't use GPT? That might be the most comfortable
> > option.
> I thought GPT was just the on-disk storage format underlying wedges.
> Was (is) that impression wrong? Perhaps GPT is a good option.
It is one way to configure wedges. See the option DKWEDGE_METHOD_GPT.
> I tried playing around with gpt(8) but wasn't able to figure out what I
> needed to tell it to get what I wanted. Perhaps I just didn't try the
> right thing; the manpage, like most manpages, is a fine reference
> document but a horrible tutorial document, and I wasn't able to get it
> to do anything but tell me it couldn't open raid0 "Device not
> configured", as in
> # gpt show ld1
> gpt: unable to open device 'rld1d': Device not configured
Hm. That works on a NetBSD 5 system I have. Looking at the history of
src/sys/dev/ld.c, at least 1.43, 1.45 and 1.47 are likely to explain
> >> There is no /dev/*dk0*, and "MAKEDEV dk0" says dk0 is an "unknown
> >> device".
> > What MAKEDEV.tmpl version is your /dev/MAKEDEV based on?
> # Generated from:
> # NetBSD: MAKEDEV.awk,v 1.15 2004/04/22 23:02:39 enami Exp
> # NetBSD: MAKEDEV.tmpl,v 188.8.131.52 2005/07/02 15:49:36 tron Exp
> # NetBSD: etc.i386/MAKEDEV.conf,v 184.108.40.206 2005/04/07 11:40:17 tron Exp
That's a MAKEDEV from netbsd-3.
> > dk supported as added in 1.59/1.60. Note that NetBSD 4.0 might not
> > have dk enabled by default in GENERIC, I think that was only changed
> > after the branch.
> I played a bit more with manually-created /dev/*dk0* based on
> sys/conf/majors. I eventually ended up with a repeatable panic when
> trying to access the /dev/rdk0a I'd created (c 168 0), so obviously
> either dk support is busted in the version I have or I was doing
> something fairly badly wrong.
That should naturally not happen, soo if you can provide the details, it
would be helpful :)
Main Index |
Thread Index |