All of lore.kernel.org
 help / color / mirror / Atom feed
From: George Mitchell <george@chinilu.com>
To: Roman Mamedov <rm@romanrm.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs on whole disk (no partitions)
Date: Sun, 22 Jun 2014 07:41:27 -0700	[thread overview]
Message-ID: <53A6EB17.2090001@chinilu.com> (raw)
In-Reply-To: <20140622201140.08e74b7e@natsu>

On 06/22/2014 07:11 AM, Roman Mamedov wrote:
> On Sun, 22 Jun 2014 06:44:13 -0700
> George Mitchell <george@chinilu.com> wrote:
>
>> 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?
>> This is a problem related to Western Digital drives.  They lie in order
>> to be compatible with older versions of Windows.
> Wake up and smell the coffee.
>
> Device Model:     HGST HTE725050A7E630
> Sector Sizes:     512 bytes logical, 4096 bytes physical
>
>
> Device Model:     TOSHIBA DT01ACA050
> Sector Sizes:     512 bytes logical, 4096 bytes physical
>
>
> The "AF" standard as accepted by the industry does include this "lying", and
> it's not just WD doing this by any stretch of the imagination. Aside from
> USB-only drives (which lack the ability to be plugged into SATA), no one can
> afford to produce and  a drive incompatible with Windows these days. In fact
> I'd be glad if you could support your Seagate 4K claim by any model names and
> their smartctl output.
>
I am not sure I see anything wrong with that.  They are showing a 
physical block size of 4096.  And it is the physical block size we care 
about.  As I recall Western Digital drives, at least in the beginning, 
were reporting 512 physical.  That was the problem.

  reply	other threads:[~2014-06-22 14:40 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 [this message]
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=53A6EB17.2090001@chinilu.com \
    --to=george@chinilu.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=rm@romanrm.net \
    /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.