Re: PDC arrays > 2 TB and non 512 byte dm sector size

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============2397499983610403515==
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature";
	boundary="------------enig0F675ABB1BAA37DDA49AA541"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig0F675ABB1BAA37DDA49AA541
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On 21/11/12 04:08 PM, Phillip Susi wrote:
> On 11/21/2012 9:19 AM, Heinz Mauelshagen wrote:
>>> No, dm goes by hard sector sizes, not pretended ones.
>=20
> What do you mean?  dm devices are virtual so there is no "hard" sector
> size; it's all virtual.  Are you saying it is hard coded to report 512
> bytes and can't be changed?

I'm guessing that what Heinz means is that dmraid reads superblocks or
whatever in accordance with the sector size on the hardware itself
("hard" =3D hardware level); since it does this in order to feed the
correct setup info to device-mapper it would not be acting on virtual
devices..

Just my interpretation though, please correct me if i'm wrong.


--------------enig0F675ABB1BAA37DDA49AA541
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)

iF4EAREIAAYFAlCvh8EACgkQ2ugaI38ACPBrvgEAuaTyaY4DEU7O+oy9dIxJIhbB
k0Eq0Ijv/DK1LDNVRgoBAI9twmP+TnLQACup16eW1bzSSFRftgBGH8uSW1bBBuKV
=yvX3
-----END PGP SIGNATURE-----

--------------enig0F675ABB1BAA37DDA49AA541--


--===============2397499983610403515==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Ataraid-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/ataraid-list
--===============2397499983610403515==--