Using a guided partitioning install of 9.0-RC2 on a 64GB (virtual) disk
(from a 9.0-RC2 ISO image) results in the following GPT partitioning:
# gpart show /dev/ada0
=> 34 134217661 ada0 GPT (64G)
34128 1 freebsd-boot (64k)
162 125828992 2 freebsd-ufs
In message <201112051743.13483.mark.martinec+free...@ijs.si>, Mark Martinec wri
tes:
>Using a guided partitioning install of 9.0-RC2 on a 64GB (virtual) disk
>(from a 9.0-RC2 ISO image) results in the following GPT partitioning:
>
># gpart show /dev/ada0
>=> 34 134217661 ada0 GPT (64G)
>
On Mon, Dec 5, 2011 at 11:47 AM, Poul-Henning Kamp wrote:
> In message <201112051743.13483.mark.martinec+free...@ijs.si>, Mark Martinec
> wri
> tes:
>>Using a guided partitioning install of 9.0-RC2 on a 64GB (virtual) disk
>>(from a 9.0-RC2 ISO image) results in the following GPT partitioning:
>>
> Btw (unrelated), tried the same with a 2 TB (virtual) disk, the
> guided partitioning suggested 64k boot, 2TB ufs, and 4GB swap,
> but then fails with "No free space left on device".
> Didn't investigate, looks like a bug.
Sorry, my mistake, please disregard this claim.
I chose "create" instead
On 12/05/11 10:47, Poul-Henning Kamp wrote:
> In message <201112051743.13483.mark.martinec+free...@ijs.si>, Mark Martinec
> wri
> tes:
>> Using a guided partitioning install of 9.0-RC2 on a 64GB (virtual) disk
>> (from a 9.0-RC2 ISO image) results in the following GPT partitioning:
>>
>> # gpart s
Nathan wrote:
> The installer will align all partitions to the GEOM stripesize/offset.
> We could make it do min(4KB, stripesize), but in general I think this is
> better done at the GEOM level.
I doubt any SSD device on the market will want to admit its
internal structure, they all claim 512 sect
> Seems to me the min(4KB,stripesize) would be a safe bet.
s/min/max/
Mark
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org
Defaulting alignment to 4kb would also help drastically in most
virtualization environments due to the underlying (and its essentially
invisible to the guest os) shared storage that is likely being used.
--
Curtis Ruck
Anytime: 347-542-7825
On Mon, Dec 5, 2011 at 12:40, Mark Martinec wrote:
> >
In message
, Maxim Khitrov writes:
>Interesting... But [...]
A "But" which I read to mean "Nahh, too hard, lets just hack it..."
I don't agree with that, we should do it right.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD comm
On Mon, Dec 5, 2011 at 1:24 PM, Poul-Henning Kamp wrote:
> In message
>
> , Maxim Khitrov writes:
>
>>Interesting... But [...]
>
> A "But" which I read to mean "Nahh, too hard, lets just hack it..."
>
> I don't agree with that, we should do it right.
How do you get around the hardware claiming
In message
, Maxim Khitrov writes:
>How do you get around the hardware claiming to use 512-byte sectors
>when it actually uses 4 kB internally?
Did you read what I wrote ?
] If the disk-driver has a 4k drive, or suspects it has a 4k drive (
] these properties are advisory only), it should anno
On 12/5/11 9:38 AM, Mark Martinec wrote:
Nathan wrote:
The installer will align all partitions to the GEOM stripesize/offset.
We could make it do min(4KB, stripesize), but in general I think this is
better done at the GEOM level.
I doubt any SSD device on the market will want to admit its
inter
12 matches
Mail list logo