From: George Mitchell <george@chinilu.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs on whole disk (no partitions)
Date: Sun, 22 Jun 2014 06:44:13 -0700 [thread overview]
Message-ID: <53A6DDAD.8070804@chinilu.com> (raw)
In-Reply-To: <CAK5rZE6gfmQsZz3W_8t=pkKEk_rzqUn5hQVv0sbt8p7qbdhSdQ@mail.gmail.com>
On 06/22/2014 12:49 AM, Imran Geriskovan wrote:
>> The 64KB Btrfs bootloader pad is 8 sector aligned, so for 512e AF disks
>> there's no problem formatting the whole drive. The alignment problem
>> actually happens when partitioning it, using old partition tools that don't
>> align on 8 sector boundaries. There are some such tools still floating
>> around.
> A 'somewhat' related question:
>
> So called Advanced Format drives has 4K physical sector size,
> however they report 512B logical sector size.
>
> How does linux kernel access those drives?
> 512B or 4K at a time?
>
> Imran
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
This is a problem related to Western Digital drives. They lie in order
to be compatible with older versions of Windows. Seagate AF drives
report 4K, not 512B. Western Digital took this path in order to make
the drives work with older Windows operating systems because Microsoft
chose not to include support for AF drives until the last minute. As
far as I know, btrfs defaults to 4K UNLESS you specify 512B when you
create the file system and the kernel follows the filesystem, not the
(in this case incorrect) info the drive reports, I could not find the
documentation to confirm this, perhaps someone else can confirm it.
Actually a 4K format will work just fine on a 512B drive AS LONG as the
alignment is correct. The larger problem occurs when a 4K drive is
formatted as 512B. But it is a real pain that the WD AF drives report
as being conventional drives in order to not confuse Windows.
next prev parent reply other threads:[~2014-06-22 13:43 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 [this message]
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
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=53A6DDAD.8070804@chinilu.com \
--to=george@chinilu.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).