> On Thu, Sep 17, 2009 at 5:11 PM,
> <[email protected]> wrote:
>
> > Disks > 1TB will just not work on a 32 bit Solaris.
> >
>
> Casper: Then this is a painful bug.
>
> Vassilis: Let me reboot into 32bit mode when I arrive at home (in a few
> hours).
> Then I will be surprised how the situation with my external 1.5TB
> disks will look like. If nothing can be done out of the box, maybe we can
> deliver a workaround-patch for VTOC stuff.
The VTOC label with disks > 1TB used to be a problem, but it
was fixed (for disks up to 2 TB) some time ago:
http://opensolaris.org/os/community/on/flag-days/pages/2008091102/
But the 2TB VTOC support does not help with the the 32-bit disk drivers
refusing access to disks > 1TB. As far as I understand it, the problem
is the daddr_t data type that is used in the kernel in a lot of places to
store a disk block number. This is defined as a 32-bit signed integer
in the 32-bit kernel. I think that this data type can't be easily changed
in the 32-bit kernel without breaking binary compatibility for existing
32-bit kernel modules.
--
This message posted from opensolaris.org
_______________________________________________
opensolaris-discuss mailing list
[email protected]
