All of lore.kernel.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs on whole disk (no partitions)
Date: Wed, 25 Jun 2014 16:01:06 +0000 (UTC)	[thread overview]
Message-ID: <pan$1341b$d2234f6c$81aec330$bd4f59f8@cox.net> (raw)
In-Reply-To: CAK5rZE4Eo+e_wbyzqPauYO=9HC9CEEF8Dftnw0D6zr1+7Z+GBw@mail.gmail.com

Imran Geriskovan posted on Wed, 25 Jun 2014 15:01:49 +0200 as excerpted:

> Note that gdisk gives default 8 sector alignment value for AF disks.
> That is 'sector' meant by gdisk is 'Logical Sector'!
> Sufficiently determined user may create misaligned partitions by playing
> with alignment value and partition start/end values.

AFAIK, for gdisk it's actually 2048 sector (1 MiB) alignment by default, 
on new devices or if you clear and redo the entire partition table.  On 
pre-partitioned devices, gdisk will attempt to identify current 
alignment, but will set 8-sector alignment on devices > 300 GiB even 
where previous alignment vales are less than that.  See the gdisk manpage 
under the "l" option for more.

The same applies to cgdisk (under the Align option in its manpage).

This has been the documented gdisk behavior for some versions now (I've 
been using it for awhile and remember when the default behavior changed), 
altho I'm referring to the 0.8.10 manpages for the version I have 
installed right now.

Tho here, I started my first partition, the BIOS boot partition, at 1 MiB 
and made it 3 MiB in size, so it ends at 4 MiB, with everything beyond 
that 4 MiB aligned.  The second partition is the EFI system partition, 
124 MiB in size so ending at 128 MiB, with everything beyond that 128 MiB 
aligned.  The next partition is /boot, 256 MiB, followed by a 640 MiB 
/var/log, ending at 1 GiB, with everything beyond that aligned on GiB 
boundaries.

That makes for easier reconstruction should I lose both copies of the GPT 
partition table. Plus, as Linus says, "real men" publish it on the net 
and then use the net for backup, and I've posted my partition table 
several times, so if I need to I can just look it up in my postings right 
here. =:^)

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman


  reply	other threads:[~2014-06-25 16:01 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-18 19:29 btrfs on whole disk (no partitions) Daniel Cegiełka
2014-06-18 20:10 ` Chris Murphy
2014-06-19 11:15   ` Austin S Hemmelgarn
2014-06-18 21:19 ` Imran Geriskovan
2014-06-19  0:07 ` Russell Coker
2014-06-19  8:58   ` Imran Geriskovan
2014-06-19  9:11     ` Imran Geriskovan
2014-06-21 19:19       ` Daniel Cegiełka
2014-06-22  1:36         ` Chris Murphy
2014-06-21 19:12   ` Daniel Cegiełka
2014-06-22  1:34     ` Chris Murphy
2014-06-22  7:49       ` Imran Geriskovan
2014-06-22 13:44         ` George Mitchell
2014-06-22 14:11           ` Roman Mamedov
2014-06-22 14:41             ` George Mitchell
2014-06-22 14:46             ` George Mitchell
2014-06-22 18:56               ` Chris Murphy
2014-06-22 18:47           ` Chris Murphy
2014-06-23  2:10             ` Duncan
2014-06-23 12:24               ` Martin K. Petersen
2014-06-24  5:37                 ` Duncan
2014-06-25 13:01                 ` Imran Geriskovan
2014-06-25 16:01                   ` Duncan [this message]
2014-06-26 18:26                     ` Imran Geriskovan
2014-06-26 18:41                   ` Chris Murphy
2014-06-26 20:46                     ` Imran Geriskovan
2014-06-22 18:31         ` Chris Murphy
2014-06-23 11:34           ` Martin K. Petersen
2014-06-19  1:01 ` George Mitchell
2014-06-19  4:52   ` Russell Coker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='pan$1341b$d2234f6c$81aec330$bd4f59f8@cox.net' \
    --to=1i5t5.duncan@cox.net \
    --cc=linux-btrfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.