From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from molly.corsac.net (pic75-3-78-194-244-226.fbxo.proxad.net [78.194.244.226]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.server123.net (Postfix) with ESMTPS for ; Tue, 5 Jan 2016 11:14:09 +0100 (CET) Message-ID: <1451988842.3914.18.camel@debian.org> From: Yves-Alexis Perez Date: Tue, 05 Jan 2016 11:14:02 +0100 In-Reply-To: <568AFA13.2010208@whgl.uni-frankfurt.de> References: <1451943067.3914.4.camel@debian.org> <568AEA2C.6010809@whgl.uni-frankfurt.de> <1451946046.3914.13.camel@debian.org> <568AFA13.2010208@whgl.uni-frankfurt.de> Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="=-YZaf3KS7pH7r0GYphTV+" Mime-Version: 1.0 Subject: Re: [dm-crypt] Alignment issue with 4K disk List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Sven Eschenberg , dm-crypt@saout.de --=-YZaf3KS7pH7r0GYphTV+ Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On mar., 2016-01-05 at 00:02 +0100, Sven Eschenberg wrote: > Hi Alexis, (Yves-Alexis actually) >=20 > I stumbled over this line: >=20 > I/O size (minimum/optimal): 4096 bytes / 33553920 bytes >=20 > The latter resembles 65535 sectors (512 Byte logical ones), which=C2=A0 > explains why the automated alignment was done at sector 65535. This=C2=A0 > value seems extremely weird though. >=20 > You said the drive was external, connected how? USB maybe? Yes. It's a Samsung T3 disk, so everything is integrated (disk+sata/usb3 adapter), not much chance I can do anything here. I'll try to force the alignment to 2048s for part1 and see what happens. >=20 > Can you take a look at hdparm -I /dev/sdc? Anything unusual there? I'll try tonight (I don't have it at hand). Thanks for the pointers though. --=20 Yves-Alexis --=-YZaf3KS7pH7r0GYphTV+ Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAABCAAGBQJWi5dqAAoJEG3bU/KmdcClltoH/iTzP0VUMKNmhsg3lPWF3wgP 1oOUQcq9aTaFIzAhKf00pIULDPPoC8H1kcNK4FnFimFNJITlifG3B+f7pRFUsXT9 jQVsLJpEUOo8qeioTZifAZXKzmWbSFn3okEQGNXgaLkvS59FuBvZTw24a1qMgDuB hUGkd+a8yO5lPtV9FdG0my8kXAfr1VdHepLmchOyD+FjXilWN3e9RHCK0OBkZC0/ tud9s2y9GrPaGzHQmoM35yoJoUZffgmH3VY/I0UqC6R2xDLmEVqx8g749fwnrMEW b9wiMsDWtqY1DfrZnltbbBQnxy3DsBg1hI2Yn5b6oYWZl2LG8bxJX5hTLDEfBxE= =LQvc -----END PGP SIGNATURE----- --=-YZaf3KS7pH7r0GYphTV+--