Date: Thu, 16 May 2019 15:35:58 -0400 From: Matthew Seaman <matthew@FreeBSD.org> To: freebsd-questions@freebsd.org Subject: Re: Suggestions for working with unstable nvme dev names in AWS Message-ID: <6d218a0d-746c-274a-fa1e-c63e2f2a0cc3@FreeBSD.org> In-Reply-To: <86623e16-744e-e366-5049-70ef69ea81df@FreeBSD.org> References: <23770.10599.687213.86492@alice.local> <08660a2a-489f-8172-22ee-47aeba315986@FreeBSD.org> <23770.58821.826610.399467@alice.local> <20190514210203.3d951fb8.freebsd@edvax.de> <23771.5612.105696.170743@alice.local> <eb1d290e48b4ba21ab350044b25592525e61457c.camel@smormegpa.no> <23771.11429.855191.658934@alice.local> <86623e16-744e-e366-5049-70ef69ea81df@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --rJ1WzMkq24oqpqvHvR75tx6Mei12Ggl55 Content-Type: multipart/mixed; boundary="gOIKjScYsLO3Eusx6kS9BKbS49eRChAJw"; protected-headers="v1" From: Matthew Seaman <matthew@FreeBSD.org> To: freebsd-questions@freebsd.org Message-ID: <6d218a0d-746c-274a-fa1e-c63e2f2a0cc3@FreeBSD.org> Subject: Re: Suggestions for working with unstable nvme dev names in AWS References: <23770.10599.687213.86492@alice.local> <08660a2a-489f-8172-22ee-47aeba315986@FreeBSD.org> <23770.58821.826610.399467@alice.local> <20190514210203.3d951fb8.freebsd@edvax.de> <23771.5612.105696.170743@alice.local> <eb1d290e48b4ba21ab350044b25592525e61457c.camel@smormegpa.no> <23771.11429.855191.658934@alice.local> <86623e16-744e-e366-5049-70ef69ea81df@FreeBSD.org> In-Reply-To: <86623e16-744e-e366-5049-70ef69ea81df@FreeBSD.org> --gOIKjScYsLO3Eusx6kS9BKbS49eRChAJw Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: quoted-printable On 15/05/2019 04:06, Matthew Seaman wrote: > This is a pretty difficult problem. Unless AWS can supply some sort of= > identification of the device beyond the /dev/nvme1 device specials or > else somehow guarantee ordering so the device names are consistent > across multiple EC2 instances then about your only possible choice is t= o > develop some heuristics like "if the device is 300MB in size then it's > the special high-IOPS device I want to use for my separate zlog." I have it on good authority that you should be able to extract the Volume ID 'vol-9999999999' from the output of nvmecontrol -- however I don't know much beyond that, and I don't have any readily accessible hardware to test against. Knowing the volume ID I believe should be sufficient for you to be able to set a meaningful glabel on the drive partitions (or however you want to do it). Cheers, Matthew --gOIKjScYsLO3Eusx6kS9BKbS49eRChAJw-- --rJ1WzMkq24oqpqvHvR75tx6Mei12Ggl55 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEEGfFU7L8RLlBUTj8wAFE/EOCp5OcFAlzdu55fFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDE5 RjE1NEVDQkYxMTJFNTA1NDRFM0YzMDAwNTEzRjEwRTBBOUU0RTcACgkQAFE/EOCp 5OcatRAAnFgiM2x+3824mD65sYnOM5+jRq3qzaaPMEtti141dYwt8lZ4UPPNY0TO ntEq5fKVxn9q6jac4pjhEesTL8NSe7Xr77SFTRebbqGNMYxD8tHUeOJqaaFoiGgV H5tdTYACezSZL9RXZqtiXE3FCQOi905j9tur4paVHiis3BkxXWERKsTXZ+17vrcE BMKo2j5ih4O9XTw+2QOvTPb9FyIK8AWOrZuAvTGjY0Dvhiyc+9uc0r1MjCZgba5r ULP6hOb51oETu/r3cddmlLXlrdYPg2kcExapAEtMzNbfGLai1ViYxQvWnz57of02 cREaTMGPWsbw8OSQTJWbhbYvhXOIY1R+1pVFkU19iJGcssNf2m73of7bhg1Ofggk jtIsOofhVRlmlPkigI08d61QMS5aDc4my0ydGn9lFlVZ5if6hU7mMJ98rwYdMUPs dUn+Edffb7xDgODwtjnGogpXPPLab1iJiqoeT/+gVmyC9gj+SLE/81N4XmmiMBcM 7SgMpHetirVnNSTGUbBVGWRJYlera6G4ndHfqX5Om1xRRK6VN4o64EquJ1CS54ch 9OjQNlrJEqqB0Cmln01Y24oK2W8LHtDUWoXA2inmHchAS/DId1IG6ocPFbKm82RU /PqLdj32Kys4w8EQtVZEqnlidzSLNtdMM7mqJttY7PMHMX0E3JY= =mZUb -----END PGP SIGNATURE----- --rJ1WzMkq24oqpqvHvR75tx6Mei12Ggl55--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6d218a0d-746c-274a-fa1e-c63e2f2a0cc3>