Re: Limit of 32GB on K15?

[Hiroyuki Yamamoto <yama1066@gmail.com>]

Hi,

Samuel Thibault wrote:
> Hiroyuki Yamamoto, le Thu 22 Nov 2007 10:05:39 +0900, a écrit :
>> K15 doesn't boot when it is in a disk image of 30GB or more though I
>> noticed when I install K15 on VMware.
>> Does the limit of 32GB exist in the kernel of Hurd?
> 
> Up to which point does it boot?
> The Mach interface talks in terms of sectors, so that should keep it up
> to 2TB.  However, there are some tricks with the disk geometry and the
> IDE interface, I'll try to see what needs to be done (I've already done
> it in the bochs bios which was limited to 128GB).


Hurd froze in 60GB disk image, in boot by the single user of the first
time after the following displays:
(snip)
start (hd0,0)/hurd/ext2fs.static: Hurd server bootstrap: ext2fs.static
[device:hd0s1] exec_

However, I'm sorry, afterwards, when having tried by 40GB disk image, it
was turned out to boot by the single user of the first time.


funky soul wrote:
> i don't know about _disk_ size limits but it might be an issue with the
> _partition_ size limit. but i'm not even sure this still applies though.
>
> Neal H. Walfield on February, 19 2007:
>> The Hurd can only support partition sizes of up to approximately two
>> gigabytes; anything larger than this will not work. This limitation
is due to
>> a design decision that was made several years ago in which the filesystem
>> server maps the entire filesystem into virtual memory. ...
>> This limitation is scheduled to be removed.
>
http://web.walfield.org/pub/people/neal/papers/hurd-installation-guide/english/hurd-install-guide.html

Samuel Thibault wrote:
> Fscking a 34GB partition works fine. Mounting it worked too, but that
> probably didn't test far sectors.


I am using the VMware disk image that makes 1GB swap partition and
remaining all of one partition.
Both of swap and the remaining Hurd partition are primary one.
Because I did not test it closely about sectors and the data of 2GB or
more used, I am not also well informed.

A peculiar phenomenon to VMware disk image might be included.


Regards,

Hiroyuki