From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 465EB678A2 for ; Tue, 10 Nov 2020 10:54:09 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 377651E4A8 for ; Tue, 10 Nov 2020 10:53:39 +0100 (CET) Received: from mail.namespace.at (mail.namespace.at [IPv6:2a01:190:1801:100::235]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id 3A11A1E49E for ; Tue, 10 Nov 2020 10:53:38 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=deduktiva.com; s=a; h=In-Reply-To:Content-Type:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=NyUzrdJ9+IvdG/LjSYkTUari9fLyHNm4F28YOxQmCZI=; b=ddQbJ23Gt6K+1fvsyBqCqCVSKs TmJkFm7/KF48VmICiVKxXAgE1iSPiX4GzDyJd29ZM+GSQoPUtR2QbTM+ShR6ljFGYS4Kal6l1dTAO 0a1bbKU2ZbY9x+zLz8iKDOHQBWDyzkMmq8/a1sPCYv4CmPw3/Uq1EjKYcUivP+7P1tiYvk9PA0QSd Ks6lOVHQ3KzP6Fa30GU3QYlCeFYIHr/fIhrdxU3xGLTYkroiqZDUn9ILMH+HRcqUgsim1SBUi5a9T LixCIK1baPbtqbuX1le0beHBwoexW7XPlKEDkkRwpR7mxDk1j+QF1Q7GAebyembR8ZCr6qKTckiaF asA5bJwg==; Date: Tue, 10 Nov 2020 10:53:31 +0100 From: Chris Hofstaedtler | Deduktiva To: Proxmox VE user list Message-ID: <20201110095331.rq2nwbvk26izj6r2@zeha.at> References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: X-SPAM-LEVEL: Spam detection results: 0 DKIM_SIGNED 0.1 Message has a DKIM or DK signature, not necessarily valid DKIM_VALID -0.1 Message has at least one valid DKIM or DK signature DKIM_VALID_AU -0.1 Message has a valid DKIM or DK signature from author's domain DKIM_VALID_EF -0.1 Message has a valid DKIM or DK signature from envelope-from domain SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [deduktiva.com] Subject: Re: [PVE-User] Matching WUI VM hardware disks to Linux guest disks X-BeenThere: pve-user@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE user list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Nov 2020 09:54:09 -0000 Hi, * Eneko Lacunza via pve-user [201110 09:03]: > I have hit a simple problem. Let be a VM with 3 disks, with .conf extract: > > scsi0: ceph-proxmox:vm-100-disk-1,cache=writeback,size=6G > scsi1: ceph-proxmox:vm-100-disk-0,cache=writeback,size=400G > scsi2: ceph-proxmox:vm-100-disk-3,cache=writeback,size=400G > > We have two virtual disks with identical size (400G). > > How can I be sure what device on Linux guest is each? You can also check - and use in /etc/fstab - the /dev/disk/by-* symlinks. In a VM, maybe the most relevant "id" is the actual path. /dev/disk/by-path has these links (in my case): pci-0000:06:05.0-scsi-0:0:0:0 -> sda pci-0000:00:05.0-scsi-0:0:0:1 -> sdb If your sdb/sdc are swapped, the SCSI IDs in the path should still be correct. If you don't like the pci path in there, /dev/disk/by-id has: scsi-0QEMU_QEMU_HARDDISK_drive-scsi0 -> sda scsi-0QEMU_QEMU_HARDDISK_drive-scsi1 -> sdb But you'll have to check if those match with the VM settings (I'd expect them to). As you've discovered and others have said, lsscsi, or lsblk -S can be used to see the SCSI IDs, too. The same info is also availabe from udevadm: udevadm info /dev/sda If you dig around in /sys, it's also there ;-) HTH, Chris -- Chris Hofstaedtler / Deduktiva GmbH (FN 418592 b, HG Wien) www.deduktiva.com / +43 1 353 1707