NetBSD Problem Report #45179
From Wolfgang.Stukenbrock@nagler-company.com Mon Jul 25 16:03:14 2011
Return-Path: <Wolfgang.Stukenbrock@nagler-company.com>
Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11])
by www.NetBSD.org (Postfix) with ESMTP id 43AC363C70A
for <gnats-bugs@gnats.NetBSD.org>; Mon, 25 Jul 2011 16:03:14 +0000 (UTC)
Message-Id: <20110725160303.B8AE111BA04E@s044.nagler-company.com>
Date: Mon, 25 Jul 2011 18:03:03 +0200 (CEST)
From: Wolfgang.Stukenbrock@nagler-company.com
Reply-To: Wolfgang.Stukenbrock@nagler-company.com
To: gnats-bugs@gnats.NetBSD.org
Subject: NetBSD disklabel does not support devices larger 2 TByte
X-Send-Pr-Version: 3.95
>Number: 45179
>Category: kern
>Synopsis: NetBSD disklabel does not support devices larger 2 TByte
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: kern-bug-people
>State: open
>Class: change-request
>Submitter-Id: net
>Arrival-Date: Mon Jul 25 16:05:00 +0000 2011
>Last-Modified: Wed Jul 27 16:25:03 +0000 2011
>Originator: Dr. Wolfgang Stukenbrock
>Release: NetBSD 5.1 - also current
>Organization:
Dr. Nagler & Company GmbH
>Environment:
System: NetBSD s044 5.1 NetBSD 5.1 (NSW-supermicro-test) #4: Mon Jul 25 14:08:22 CEST 2011 wgstuken@s012:/export/NetBSD-5.1/N+C-build/.OBJDIR_amd64/export/NetBSD-5.1/src/sys/arch/amd64/compile/NSW-supermicro-test amd64
Architecture: x86_64
Machine: amd64
>Description:
The partition size and the offset fields in the disklabel structure for patitions is only 32-bit.
If you have a larger disk or stripe some disks via raidframe, you may end up in a disk bejong 2 TByte.
In such a situtation the current implementation of the NetBSD disklabel makes makes everything behind the first
2 TByte unavailable.
Accedently the value is not clamped to 0xffffffff by the disklabel program. The additional bits are simply dropped
and this can result in a very small disk size, if the real size is e.g. 0x204000000 (-> 0x0400000).
The problem also appears on (external) HW-raid-controler that offer a large "disk" that should be partitioned by the
operating system into smaller peaces.
>How-To-Repeat:
Stripe some disk with raidframe. You will get problems putting a disklabel on it if the size exceeds 2 TByte.
>Fix:
A new version of the disklabel structure is needed with 64 bit fields for the partition information and at least some other
disk describing fields.
The kernel and other disklabel-processing programs - such as disklabel - must be extended. (I do not know the complete
list of affected programs till now - sorry)
Accedently I need this "now", but have no time to port it. Sorry.
>Audit-Trail:
From: Martin Husemann <martin@duskware.de>
To: gnats-bugs@NetBSD.org
Cc: kern-bug-people@netbsd.org, gnats-admin@netbsd.org,
netbsd-bugs@netbsd.org
Subject: Re: kern/45179: NetBSD disklabel does not support devices larger 2 TByte
Date: Mon, 25 Jul 2011 18:09:16 +0200
It is already there:
See gpt(8) for a replacement of the disklabel(8) program and dk(4) for
usage of the generated "partitions".
Disklabel will not be extended.
Martin
From: christos@zoulas.com (Christos Zoulas)
To: gnats-bugs@NetBSD.org, kern-bug-people@netbsd.org,
gnats-admin@netbsd.org, netbsd-bugs@netbsd.org
Cc:
Subject: Re: kern/45179: NetBSD disklabel does not support devices larger 2 TByte
Date: Mon, 25 Jul 2011 12:27:31 -0400
On Jul 25, 4:05pm, Wolfgang.Stukenbrock@nagler-company.com (Wolfgang.Stukenbrock@nagler-company.com) wrote:
-- Subject: kern/45179: NetBSD disklabel does not support devices larger 2 TB
| The partition size and the offset fields in the disklabel structure for patitions is only 32-bit.
| If you have a larger disk or stripe some disks via raidframe, you may end up in a disk bejong 2 TByte.
| In such a situtation the current implementation of the NetBSD disklabel makes makes everything behind the first
| 2 TByte unavailable.
| Accedently the value is not clamped to 0xffffffff by the disklabel program. The additional bits are simply dropped
| and this can result in a very small disk size, if the real size is e.g. 0x204000000 (-> 0x0400000).
| The problem also appears on (external) HW-raid-controler that offer a large "disk" that should be partitioned by the
| operating system into smaller peaces.
| >How-To-Repeat:
| Stripe some disk with raidframe. You will get problems putting a disklabel on it if the size exceeds 2 TByte.
| >Fix:
| A new version of the disklabel structure is needed with 64 bit fields for the partition information and at least some other
| disk describing fields.
| The kernel and other disklabel-processing programs - such as disklabel - must be extended. (I do not know the complete
| list of affected programs till now - sorry)
| Accedently I need this "now", but have no time to port it. Sorry.
Can't you use wedges and gpt?
christos
From: Hauke Fath <hauke@Espresso.Rhein-Neckar.DE>
To: christos@zoulas.com (Christos Zoulas)
Cc: gnats-bugs@NetBSD.org, kern-bug-people@NetBSD.org
Subject: Re: kern/45179: NetBSD disklabel does not support devices larger
2 TByte
Date: Mon, 25 Jul 2011 21:02:25 +0200
At 12:27 Uhr -0400 25.7.2011, Christos Zoulas wrote:
>Can't you use wedges and gpt?
Since Wolfgang mentioned raidframe: RAID level 1 wedges on gpt disks are
not bootable.
hauke
--
"It's never straight up and down" (DEVO)
From: eric@cirr.com (Eric Schnoebelen)
To: gnats-bugs@NetBSD.org
Cc: kern-bug-people@NetBSD.org, gnats-admin@NetBSD.org, netbsd-bugs@NetBSD.org,
Wolfgang.Stukenbrock@nagler-company.com
Subject: Re: kern/45179: NetBSD disklabel does not support devices larger 2 TByte
Date: Mon, 25 Jul 2011 18:46:46 -0500
Hauke Fath writes:
- At 12:27 Uhr -0400 25.7.2011, Christos Zoulas wrote:
- >Can't you use wedges and gpt?
-
- Since Wolfgang mentioned raidframe: RAID level 1 wedges on gpt disks are
- not bootable.
Please don't tell my systems..
I have pairs of wedges in a RAID1 booting just fine.
The raid0d is internal labelled with a disklabel, rather than a
nested wedge device.
I haven't tried a nested wedge-on-raid-on-wedge config.
--
Eric Schnoebelen eric@cirr.com http://www.cirr.com
"Don't ever speak more clearly than you think..." -- Neils Bohr
From: christos@zoulas.com (Christos Zoulas)
To: Hauke Fath <hauke@Espresso.Rhein-Neckar.DE>
Cc: gnats-bugs@NetBSD.org, kern-bug-people@NetBSD.org
Subject: Re: kern/45179: NetBSD disklabel does not support devices larger 2 TByte
Date: Mon, 25 Jul 2011 20:47:14 -0400
On Jul 25, 9:02pm, hauke@Espresso.Rhein-Neckar.DE (Hauke Fath) wrote:
-- Subject: Re: kern/45179: NetBSD disklabel does not support devices larger
| At 12:27 Uhr -0400 25.7.2011, Christos Zoulas wrote:
| >Can't you use wedges and gpt?
|
| Since Wolfgang mentioned raidframe: RAID level 1 wedges on gpt disks are
| not bootable.
It is not that difficult to make gpt booting work, we just need to write
or copy some code.
christos
From: Hauke Fath <hauke@Espresso.Rhein-Neckar.DE>
To: eric@cirr.com (Eric Schnoebelen)
Cc: gnats-bugs@NetBSD.org, kern-bug-people@NetBSD.org, gnats-admin@NetBSD.org
Subject: Re: kern/45179: NetBSD disklabel does not support devices larger
2 TByte
Date: Tue, 26 Jul 2011 09:07:31 +0200
At 18:46 Uhr -0500 25.7.2011, Eric Schnoebelen wrote:
>The raid0d is internal labelled with a disklabel, rather than a
>nested wedge device.
You're cheating. ;)
>I haven't tried a nested wedge-on-raid-on-wedge config.
I have. It doesn't work.
hauke
--
"It's never straight up and down" (DEVO)
From: Wolfgang Stukenbrock <Wolfgang.Stukenbrock@nagler-company.com>
To: gnats-bugs@NetBSD.org
Cc: kern-bug-people@NetBSD.org, gnats-admin@NetBSD.org, netbsd-bugs@NetBSD.org,
Wolfgang.Stukenbrock@nagler-company.com
Subject: Re: kern/45179: NetBSD disklabel does not support devices larger 2 TByte
Date: Wed, 27 Jul 2011 11:35:59 +0200
Hi,
if it is "just copy some code", then that should be done in order to be
able to boot from large devices. The time when the first 4 TByte discs
will be available may be soon ...
The current hack in the bootloader code just try to get a valid
disklabel 64 block's later for booting from a raid1 device. That is a
very simple sollution.
I will have look at gtp(8). Perhaps this will solve my problem.
If disklabel is supposed to retire, than the sysinst should "always"
install systems useing gtp as soon as possible.
On the other hand, the extensions to the disklabel structure does not
sound very expensive to me - I only have no time to do it (and test on
"all" architectures).
best regards
W. Stukenbrock
Christos Zoulas wrote:
> The following reply was made to PR kern/45179; it has been noted by GNATS.
>
> From: christos@zoulas.com (Christos Zoulas)
> To: Hauke Fath <hauke@Espresso.Rhein-Neckar.DE>
> Cc: gnats-bugs@NetBSD.org, kern-bug-people@NetBSD.org
> Subject: Re: kern/45179: NetBSD disklabel does not support devices larger 2 TByte
> Date: Mon, 25 Jul 2011 20:47:14 -0400
>
> On Jul 25, 9:02pm, hauke@Espresso.Rhein-Neckar.DE (Hauke Fath) wrote:
> -- Subject: Re: kern/45179: NetBSD disklabel does not support devices larger
>
> | At 12:27 Uhr -0400 25.7.2011, Christos Zoulas wrote:
> | >Can't you use wedges and gpt?
> |
> | Since Wolfgang mentioned raidframe: RAID level 1 wedges on gpt disks are
> | not bootable.
>
> It is not that difficult to make gpt booting work, we just need to write
> or copy some code.
>
> christos
>
>
>
>
--
Dr. Nagler & Company GmbH
Hauptstraße 9
92253 Schnaittenbach
Tel. +49 9622/71 97-42
Fax +49 9622/71 97-50
Wolfgang.Stukenbrock@nagler-company.com
http://www.nagler-company.com
Hauptsitz: Schnaittenbach
Handelregister: Amberg HRB
Gerichtsstand: Amberg
Steuernummer: 201/118/51825
USt.-ID-Nummer: DE 273143997
Geschäftsführer: Dr. Martin Nagler, Dr. Dr. Karl-Kuno Kunze
From: Wolfgang Stukenbrock <Wolfgang.Stukenbrock@nagler-company.com>
To: gnats-bugs@NetBSD.org
Cc: kern-bug-people@NetBSD.org, gnats-admin@NetBSD.org, netbsd-bugs@NetBSD.org,
Wolfgang.Stukenbrock@nagler-company.com
Subject: Re: kern/45179: NetBSD disklabel does not support devices larger 2 TByte
Date: Wed, 27 Jul 2011 11:57:14 +0200
Hi again,
now I've a look at gpt(8).
the manual say:
By default, one cannot create a GPT when the device contains a
MBR, however this can be overridden with the -f option. If the
-f option is specified, an existing MBR is destroyed and any par-
titions described by the MBR are lost.
This means, gpt(8) is not usable on (at least) i386 and amd64
architectures for root disks!
So gpt is no sollution for theese architectures!
I know that Sun supports something called EFI-disklabels (as far as I
remember - perhaps the name was different ...).
I've got lots of problems with them on a X86-Sun some time ago.
But perhaps I simply does something wrong.
Is there support for such a thing in NetBSD?
best regaurds
W. Stukenbrock
Wolfgang Stukenbrock wrote:
> The following reply was made to PR kern/45179; it has been noted by GNATS.
>
> From: Wolfgang Stukenbrock <Wolfgang.Stukenbrock@nagler-company.com>
> To: gnats-bugs@NetBSD.org
> Cc: kern-bug-people@NetBSD.org, gnats-admin@NetBSD.org, netbsd-bugs@NetBSD.org,
> Wolfgang.Stukenbrock@nagler-company.com
> Subject: Re: kern/45179: NetBSD disklabel does not support devices larger 2 TByte
> Date: Wed, 27 Jul 2011 11:35:59 +0200
>
> Hi,
>
> if it is "just copy some code", then that should be done in order to be
> able to boot from large devices. The time when the first 4 TByte discs
> will be available may be soon ...
> The current hack in the bootloader code just try to get a valid
> disklabel 64 block's later for booting from a raid1 device. That is a
> very simple sollution.
>
> I will have look at gtp(8). Perhaps this will solve my problem.
>
> If disklabel is supposed to retire, than the sysinst should "always"
> install systems useing gtp as soon as possible.
> On the other hand, the extensions to the disklabel structure does not
> sound very expensive to me - I only have no time to do it (and test on
> "all" architectures).
>
> best regards
>
> W. Stukenbrock
>
> Christos Zoulas wrote:
>
> > The following reply was made to PR kern/45179; it has been noted by GNATS.
> >
> > From: christos@zoulas.com (Christos Zoulas)
> > To: Hauke Fath <hauke@Espresso.Rhein-Neckar.DE>
> > Cc: gnats-bugs@NetBSD.org, kern-bug-people@NetBSD.org
> > Subject: Re: kern/45179: NetBSD disklabel does not support devices larger 2 TByte
> > Date: Mon, 25 Jul 2011 20:47:14 -0400
> >
> > On Jul 25, 9:02pm, hauke@Espresso.Rhein-Neckar.DE (Hauke Fath) wrote:
> > -- Subject: Re: kern/45179: NetBSD disklabel does not support devices larger
> >
> > | At 12:27 Uhr -0400 25.7.2011, Christos Zoulas wrote:
> > | >Can't you use wedges and gpt?
> > |
> > | Since Wolfgang mentioned raidframe: RAID level 1 wedges on gpt disks are
> > | not bootable.
> >
> > It is not that difficult to make gpt booting work, we just need to write
> > or copy some code.
> >
> > christos
> >
> >
> >
> >
>
>
> --
>
>
> Dr. Nagler & Company GmbH
> Hauptstraße 9
> 92253 Schnaittenbach
>
> Tel. +49 9622/71 97-42
> Fax +49 9622/71 97-50
>
> Wolfgang.Stukenbrock@nagler-company.com
> http://www.nagler-company.com
>
>
> Hauptsitz: Schnaittenbach
> Handelregister: Amberg HRB
> Gerichtsstand: Amberg
> Steuernummer: 201/118/51825
> USt.-ID-Nummer: DE 273143997
> Geschäftsführer: Dr. Martin Nagler, Dr. Dr. Karl-Kuno Kunze
>
>
>
>
>
--
Dr. Nagler & Company GmbH
Hauptstraße 9
92253 Schnaittenbach
Tel. +49 9622/71 97-42
Fax +49 9622/71 97-50
Wolfgang.Stukenbrock@nagler-company.com
http://www.nagler-company.com
Hauptsitz: Schnaittenbach
Handelregister: Amberg HRB
Gerichtsstand: Amberg
Steuernummer: 201/118/51825
USt.-ID-Nummer: DE 273143997
Geschäftsführer: Dr. Martin Nagler, Dr. Dr. Karl-Kuno Kunze
From: Martin Husemann <martin@duskware.de>
To: Wolfgang Stukenbrock <Wolfgang.Stukenbrock@nagler-company.com>
Cc: gnats-bugs@NetBSD.org
Subject: Re: kern/45179: NetBSD disklabel does not support devices larger 2 TByte
Date: Wed, 27 Jul 2011 12:10:25 +0200
On Wed, Jul 27, 2011 at 11:35:59AM +0200, Wolfgang Stukenbrock wrote:
> The current hack in the bootloader code just try to get a valid
> disklabel 64 block's later for booting from a raid1 device. That is a
> very simple sollution.
It is a tiny bit more complex: the GPT entry is of type
GPT_ENT_TYPE_NETBSD_RAIDFRAME instead of GPT_ENT_TYPE_NETBSD_FFS,
so the whole loop would need to match both GUIDs and if it is a RAIDFRAME
match, offset the superblock-LBA by 64.
> If disklabel is supposed to retire, than the sysinst should "always"
> install systems useing gtp as soon as possible.
Yes, but it is not quite trivial, because for example Windows 7 (even SP1)
can not share the boot disk if it is partitioned with GPT.
For a NetBSD only setups, I agree (and intend do make it so).
> On the other hand, the extensions to the disklabel structure does not
> sound very expensive to me - I only have no time to do it (and test on
> "all" architectures).
disklabel has to die, ASAP!
Besides, quite a few archs can not extend the on-disk version of the disklabel,
as that would make them incompatible with their firmware.
Martin
From: Martin Husemann <martin@duskware.de>
To: Wolfgang Stukenbrock <Wolfgang.Stukenbrock@nagler-company.com>
Cc: gnats-bugs@NetBSD.org, kern-bug-people@NetBSD.org,
gnats-admin@NetBSD.org, netbsd-bugs@NetBSD.org
Subject: Re: kern/45179: NetBSD disklabel does not support devices larger 2 TByte
Date: Wed, 27 Jul 2011 12:12:06 +0200
On Wed, Jul 27, 2011 at 11:57:14AM +0200, Wolfgang Stukenbrock wrote:
> This means, gpt(8) is not usable on (at least) i386 and amd64
> architectures for root disks!
No, that is not true. I recently booted a amd64 machine from a gpt labeld
disk. Firmware in all "recent" machines does handle it just fine.
Martin
From: Manuel Bouyer <bouyer@antioche.eu.org>
To: Wolfgang Stukenbrock <Wolfgang.Stukenbrock@nagler-company.com>
Cc: gnats-bugs@NetBSD.org, kern-bug-people@NetBSD.org, gnats-admin@NetBSD.org,
netbsd-bugs@NetBSD.org
Subject: Re: kern/45179: NetBSD disklabel does not support devices larger 2
TByte
Date: Wed, 27 Jul 2011 13:19:14 +0200
On Wed, Jul 27, 2011 at 11:57:14AM +0200, Wolfgang Stukenbrock wrote:
> Hi again,
>
> now I've a look at gpt(8).
>
> the manual say:
>
> By default, one cannot create a GPT when the device contains a
> MBR, however this can be overridden with the -f option. If the
> -f option is specified, an existing MBR is destroyed and any par-
> titions described by the MBR are lost.
>
> This means, gpt(8) is not usable on (at least) i386 and amd64
> architectures for root disks!
> So gpt is no sollution for theese architectures!
It is, gpt-partitionned disks are bootable.
MBRs also have a size limitation, which may also be a 2TB.
--
Manuel Bouyer <bouyer@antioche.eu.org>
NetBSD: 26 ans d'experience feront toujours la difference
--
From: Wolfgang Stukenbrock <Wolfgang.Stukenbrock@nagler-company.com>
To: gnats-bugs@NetBSD.org
Cc: kern-bug-people@NetBSD.org, gnats-admin@NetBSD.org, netbsd-bugs@NetBSD.org,
Wolfgang.Stukenbrock@nagler-company.com
Subject: Re: kern/45179: NetBSD disklabel does not support devices larger 2 TByte
Date: Wed, 27 Jul 2011 14:21:36 +0200
Hi,
OK. If it is possible to boot from that, it would be fine for my current
needs.
The Windows-problem does not hurt me - at least for the systems where I
need this.
Is it planned to extend the boot code to boot from a RAID1 setup in gpt
in the near future?
At the moment I think this PR can be closed as soon as the bootsupport
for raid1 partitions is added to gpt.
I need this in 5.x as soon as possible for new "productive" systems, but
I can do the integration from current into "my" 5.x-version by myself if
it is inserted only for 6.x or later. Accedently I've no time to figure
out all required changes myself
best regards
W. Stukenbrock
Martin Husemann wrote:
> The following reply was made to PR kern/45179; it has been noted by GNATS.
>
> From: Martin Husemann <martin@duskware.de>
> To: Wolfgang Stukenbrock <Wolfgang.Stukenbrock@nagler-company.com>
> Cc: gnats-bugs@NetBSD.org, kern-bug-people@NetBSD.org,
> gnats-admin@NetBSD.org, netbsd-bugs@NetBSD.org
> Subject: Re: kern/45179: NetBSD disklabel does not support devices larger 2 TByte
> Date: Wed, 27 Jul 2011 12:12:06 +0200
>
> On Wed, Jul 27, 2011 at 11:57:14AM +0200, Wolfgang Stukenbrock wrote:
> > This means, gpt(8) is not usable on (at least) i386 and amd64
> > architectures for root disks!
>
> No, that is not true. I recently booted a amd64 machine from a gpt labeld
> disk. Firmware in all "recent" machines does handle it just fine.
>
> Martin
>
>
>
>
--
Dr. Nagler & Company GmbH
Hauptstraße 9
92253 Schnaittenbach
Tel. +49 9622/71 97-42
Fax +49 9622/71 97-50
Wolfgang.Stukenbrock@nagler-company.com
http://www.nagler-company.com
Hauptsitz: Schnaittenbach
Handelregister: Amberg HRB
Gerichtsstand: Amberg
Steuernummer: 201/118/51825
USt.-ID-Nummer: DE 273143997
Geschäftsführer: Dr. Martin Nagler, Dr. Dr. Karl-Kuno Kunze
From: Wolfgang Stukenbrock <Wolfgang.Stukenbrock@nagler-company.com>
To: gnats-bugs@NetBSD.org
Cc: kern-bug-people@NetBSD.org, gnats-admin@NetBSD.org, netbsd-bugs@NetBSD.org,
Wolfgang.Stukenbrock@nagler-company.com
Subject: Re: kern/45179: NetBSD disklabel does not support devices larger 2 TByte
Date: Wed, 27 Jul 2011 18:24:28 +0200
Hi, again ...
Now I've played a little bit around with gpt and dkctl ....
First impression: complicate, not intentive and very fault intensive
OK. by adding a GPT label to the "raw" disk (e.g. sd6) the avaliable
size shrinks.
Bad - because a migration of existing setups is impossible ....
But for new setups that is OK.
I now can setup two "scsi" disks - in real two SATA disks on two mfi
controlers - and setup a RAID1 device of them.
(To get better fault security you should not setup two disks on the same
HW-controler as a RAID1 device ... If the controler gets into trouble
you loose the filesystem.)
I can do this again with other pairs of disks.
remark: now I've already used 2 * number of raiddevices dk(4) devices ...
Next I need to setup a GPT label on all created raid devices.
remark: additional number of raiddevices dk(4) nodes used
Then I create a RAID0 device of the dk(4) devices build in the previous
step.
I need another dk(4) device node for the main partition on that device then.
OK setting up this all by hand works fine.
newfs is still running ...
But what about autoconfigure code?
I've send a patch (a long time ago for 4.x (PR39784) in 2008) for the
autoconfig stuff of raidframe that enables raidframe of setup layered
deviced (used in the setup here) during autoconfig.
At least in 5.1 it is still not in, but otherwise no change to setup
layered devices in autoconfig in a relyable manner.
But does the autoconfig code setup the correct dk(4) devices after each
raidframe configuration?
A reboot ends up in a desaster !
The wedge on sd6 has now type NetBSD UFS/UFS2 ???
It was setup as RAID before and was reported as RAIDframe wedge.
So the raid device based on this partition has not been setup, resulting
in RAID0 setup of the layered device to fail too, because the components
has not been setup correctly.
Any Idea what might have happend to the wedge information?
best regards
W. Stukenbrock
But neverless the endless number of intermediate df(4) devices just for
building the raid abstractions is a pain!
Wolfgang Stukenbrock wrote:
> The following reply was made to PR kern/45179; it has been noted by GNATS.
>
> From: Wolfgang Stukenbrock <Wolfgang.Stukenbrock@nagler-company.com>
> To: gnats-bugs@NetBSD.org
> Cc: kern-bug-people@NetBSD.org, gnats-admin@NetBSD.org, netbsd-bugs@NetBSD.org,
> Wolfgang.Stukenbrock@nagler-company.com
> Subject: Re: kern/45179: NetBSD disklabel does not support devices larger 2 TByte
> Date: Wed, 27 Jul 2011 14:21:36 +0200
>
> Hi,
>
> OK. If it is possible to boot from that, it would be fine for my current
> needs.
> The Windows-problem does not hurt me - at least for the systems where I
> need this.
>
> Is it planned to extend the boot code to boot from a RAID1 setup in gpt
> in the near future?
>
> At the moment I think this PR can be closed as soon as the bootsupport
> for raid1 partitions is added to gpt.
> I need this in 5.x as soon as possible for new "productive" systems, but
> I can do the integration from current into "my" 5.x-version by myself if
> it is inserted only for 6.x or later. Accedently I've no time to figure
> out all required changes myself
>
> best regards
>
> W. Stukenbrock
>
> Martin Husemann wrote:
>
> > The following reply was made to PR kern/45179; it has been noted by GNATS.
> >
> > From: Martin Husemann <martin@duskware.de>
> > To: Wolfgang Stukenbrock <Wolfgang.Stukenbrock@nagler-company.com>
> > Cc: gnats-bugs@NetBSD.org, kern-bug-people@NetBSD.org,
> > gnats-admin@NetBSD.org, netbsd-bugs@NetBSD.org
> > Subject: Re: kern/45179: NetBSD disklabel does not support devices larger 2 TByte
> > Date: Wed, 27 Jul 2011 12:12:06 +0200
> >
> > On Wed, Jul 27, 2011 at 11:57:14AM +0200, Wolfgang Stukenbrock wrote:
> > > This means, gpt(8) is not usable on (at least) i386 and amd64
> > > architectures for root disks!
> >
> > No, that is not true. I recently booted a amd64 machine from a gpt labeld
> > disk. Firmware in all "recent" machines does handle it just fine.
> >
> > Martin
> >
> >
> >
> >
>
>
> --
>
>
> Dr. Nagler & Company GmbH
> Hauptstraße 9
> 92253 Schnaittenbach
>
> Tel. +49 9622/71 97-42
> Fax +49 9622/71 97-50
>
> Wolfgang.Stukenbrock@nagler-company.com
> http://www.nagler-company.com
>
>
> Hauptsitz: Schnaittenbach
> Handelregister: Amberg HRB
> Gerichtsstand: Amberg
> Steuernummer: 201/118/51825
> USt.-ID-Nummer: DE 273143997
> Geschäftsführer: Dr. Martin Nagler, Dr. Dr. Karl-Kuno Kunze
>
>
>
>
>
--
Dr. Nagler & Company GmbH
Hauptstraße 9
92253 Schnaittenbach
Tel. +49 9622/71 97-42
Fax +49 9622/71 97-50
Wolfgang.Stukenbrock@nagler-company.com
http://www.nagler-company.com
Hauptsitz: Schnaittenbach
Handelregister: Amberg HRB
Gerichtsstand: Amberg
Steuernummer: 201/118/51825
USt.-ID-Nummer: DE 273143997
Geschäftsführer: Dr. Martin Nagler, Dr. Dr. Karl-Kuno Kunze
>Unformatted:
(Contact us)
$NetBSD: query-full-pr,v 1.39 2013/11/01 18:47:49 spz Exp $
$NetBSD: gnats_config.sh,v 1.8 2006/05/07 09:23:38 tsutsui Exp $
Copyright © 1994-2007
The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.
Home