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