1 |
On Fri, Feb 12, 2010 at 1:06 AM, Mick <michaelkintzios@×××××.com> wrote: |
2 |
> On Tuesday 09 February 2010 16:31:15 Mark Knecht wrote: |
3 |
>> On Mon, Feb 8, 2010 at 4:37 PM, Mark Knecht <markknecht@×××××.com> wrote: |
4 |
>> <SNIP> |
5 |
>> |
6 |
>> > There's a few small downsides I've run into with all of this so far: |
7 |
>> > |
8 |
>> > 1) Since we don't use sector 63 it seems that fdisk will still tell |
9 |
>> > you that you can use 63 until you use up all your primary partitions. |
10 |
>> > It used to be easier to put additional partitions on when it gave you |
11 |
>> > the next sector you could use after the one you just added.. Now I'm |
12 |
>> > finding that I need to write things down and figure it out more |
13 |
>> > carefully outside of fdisk. |
14 |
>> |
15 |
>> Replying mostly to myself, WRT the value 63 continuing to show up |
16 |
>> after making the first partition start at 64, in my case since for |
17 |
>> desktop machines the first partition is general /boot, and as it's |
18 |
>> written and read so seldom, in the future when faced with this problem |
19 |
>> I will likely start /boot at 63 and just ensure that all the other |
20 |
>> partitions - /, /var, /home, etc., start on boundaries divisible by 8. |
21 |
>> |
22 |
>> It will make using fdisk slightly more pleasant. |
23 |
> |
24 |
> I noticed while working on two new laptops with gparted that resizing Windows |
25 |
> 7 and creating new partitions showed up small blank partitions (marked as |
26 |
> hidden) in between the resized, and/or the new partitions. If I recall |
27 |
> correctly these were only a few KB each so rather small as such. I am not |
28 |
> sure why gparted created these - could it be related to the drive |
29 |
> automatically aligning partitions to this 4K sector size that is discussed |
30 |
> here? |
31 |
> -- |
32 |
> Regards, |
33 |
> Mick |
34 |
> |
35 |
|
36 |
http://lkml.indiana.edu/hypermail/linux/kernel/0902.3/01024.html |
37 |
|
38 |
Cheers, |
39 |
Mark |