From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: device-mapper development <dm-devel@redhat.com>
Cc: Alasdair G Kergon <agk@redhat.com>, Mike Snitzer <snitzer@redhat.com>
Subject: Re: [PATCH 4/4] Test chunk size against both origin and snapshot sector size
Date: Mon, 15 Mar 2010 12:53:43 -0400 [thread overview]
Message-ID: <yq13a01frvs.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <Pine.LNX.4.64.1003151151370.2471@hs20-bc2-1.build.redhat.com> (Mikulas Patocka's message of "Mon, 15 Mar 2010 11:52:56 -0400 (EDT)")
>>>>> "Mikulas" == Mikulas Patocka <mpatocka@redhat.com> writes:
>> Do you mean something like 512b logical and 4K physical? Such
>> devices must perform the appropriate r-m-w. A 4K formatted device
>> will report 4K for both logical and physical (unless the device and
>> format tool allows for physical != logical).
>>
>> Mike
Mikulas> No, I meant what happens if you format it with 514, 516, etc
Mikulas> physical blocksize. the Linux clearly doesn't support it, so
Mikulas> what will it do with it? I'll try when I finish tests on 4K.
We only support powers of two (except when the drive is formatted with
DIF but even in that case the logical_block_size is a power of two).
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2010-03-15 16:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-15 6:04 [PATCH 4/4] Test chunk size against both origin and snapshot sector size Mikulas Patocka
2010-03-15 14:52 ` Mike Snitzer
2010-03-15 15:10 ` Mikulas Patocka
2010-03-15 15:30 ` Mike Snitzer
2010-03-15 15:52 ` Mikulas Patocka
2010-03-15 16:53 ` Martin K. Petersen [this message]
2010-03-15 15:54 ` Mikulas Patocka
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=yq13a01frvs.fsf@sermon.lab.mkp.net \
--to=martin.petersen@oracle.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=snitzer@redhat.com \
/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.