From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <rightkicktech@gmail.com>
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) server-digest SHA256)
 (No client certificate requested)
 by lists.proxmox.com (Postfix) with ESMTPS id BCA1E74280
 for <pve-user@lists.proxmox.com>; Tue, 31 May 2022 17:18:16 +0200 (CEST)
Received: from firstgate.proxmox.com (localhost [127.0.0.1])
 by firstgate.proxmox.com (Proxmox) with ESMTP id B002FAF70
 for <pve-user@lists.proxmox.com>; Tue, 31 May 2022 17:18:16 +0200 (CEST)
Received: from mail-io1-xd2b.google.com (mail-io1-xd2b.google.com
 [IPv6:2607:f8b0:4864:20::d2b])
 (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits)
 key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256)
 (No client certificate requested)
 by firstgate.proxmox.com (Proxmox) with ESMTPS id 22D72AF60
 for <pve-user@lists.proxmox.com>; Tue, 31 May 2022 17:18:16 +0200 (CEST)
Received: by mail-io1-xd2b.google.com with SMTP id 2so14443140iou.5
 for <pve-user@lists.proxmox.com>; Tue, 31 May 2022 08:18:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112;
 h=mime-version:from:date:message-id:subject:to;
 bh=VPQnqToRDJwtYzpgRaP1sCcxY7sQMIxf1kSGiKG0cIY=;
 b=WwXIj9KgaMGPx9nrWOWdLQQ3RTubUH+4IkYPxi/jpEnxK7M0D1li5LMJ6vztRS7Uk8
 72yC3z8MXoc33OyJ/iThrITJ1TwrQ1PfWASjh33oy24xWGmT2oTZFwnPq8EsuTg2jN7o
 avkMebZyNCskeMSBwG6hDLjpWim9y75gK1YEhIOTjVERAtnLuJaOg7haQWZjS35h878P
 XmNJYBg2w2i8HB7ta+dZWCRnWnHRSnZs5njLQ0/c2CzVOnAmlSB+GGJ4ejT4BoJqVLdV
 jj1CIxnrN40iwpfXYxaAL++F5tiL+lsq607Feyx2+7courTTCHu0KGcZPPU7z0uw4gWY
 89hQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20210112;
 h=x-gm-message-state:mime-version:from:date:message-id:subject:to;
 bh=VPQnqToRDJwtYzpgRaP1sCcxY7sQMIxf1kSGiKG0cIY=;
 b=U5Ou0nXFcIIrA3bcTjsb5V44CB3akr3FYhdFTl3e85A0KAM8nf3QOmSJlMaEROnmN9
 ivZHvCKAiVwVBpnJXuE+nJvPCb2Zh4GC1kSWJPE4Zpnc4zwP7pq8+BsV56SkL866CO0J
 peozMD9Uz1al0Eo4nKFXxWBiH+7YwE8oDyvuk4+8ovES6JGP1BkzvnbLd4wOo5W7421O
 SVWVqbfkXMngA3iJdV6Q6CcjjfXlcCldb361j0iqwGdNAHd11aXq1Xq0mKl1+JRJFwir
 IYvX7zPyvXBwHi/7hXWmNNgjGis9+POa4EQ+Htu8s/RzeT+Y2nCRePHIisHExM6anTkW
 hePQ==
X-Gm-Message-State: AOAM5312QXSje8gcZ/ZcX8m4w/L240gMUG9EI++nbFhDZKaUG0Sl2Ctt
 FWDACPa1n8+CKbkR0KgeTp0Dw8EYcc9V24r3k13zKic/jA==
X-Google-Smtp-Source: ABdhPJyz8owW99Ppq4dZKDWPf/6tAzDUyFz1KnYzbHszfxAPjFgvX7Y5WgRARWkXW2E92Tv+aNH3/FuCy9neXMFjWnw=
X-Received: by 2002:a02:6a6b:0:b0:323:fcf9:2227 with SMTP id
 m43-20020a026a6b000000b00323fcf92227mr30736417jaf.137.1654010288495; Tue, 31
 May 2022 08:18:08 -0700 (PDT)
MIME-Version: 1.0
From: Alex K <rightkicktech@gmail.com>
Date: Tue, 31 May 2022 18:17:57 +0300
Message-ID: <CABMULtJUs5ckwkBf+fFh2FPy6HvMwE_Tu3pdz7Ya2xMnoYfiqw@mail.gmail.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
X-SPAM-LEVEL: Spam detection results:  0
 BAYES_00                 -1.9 Bayes spam probability is 0 to 1%
 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
 FREEMAIL_FROM 0.001 Sender email is commonly abused enduser mail provider
 HTML_MESSAGE            0.001 HTML included in message
 RCVD_IN_DNSWL_NONE     -0.0001 Sender listed at https://www.dnswl.org/,
 no trust
 SPF_HELO_NONE           0.001 SPF: HELO does not publish an SPF Record
 SPF_PASS               -0.001 SPF: sender matches SPF record
 T_SCC_BODY_TEXT_LINE    -0.01 -
Content-Type: text/plain; charset="UTF-8"
X-Content-Filtered-By: Mailman/MimeDel 2.1.29
Subject: [PVE-User] Mount issue of thin LVM on boot
X-BeenThere: pve-user@lists.proxmox.com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Proxmox VE user list <pve-user.lists.proxmox.com>
List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-user>, 
 <mailto:pve-user-request@lists.proxmox.com?subject=unsubscribe>
List-Archive: <http://lists.proxmox.com/pipermail/pve-user/>
List-Post: <mailto:pve-user@lists.proxmox.com>
List-Help: <mailto:pve-user-request@lists.proxmox.com?subject=help>
List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user>, 
 <mailto:pve-user-request@lists.proxmox.com?subject=subscribe>
X-List-Received-Date: Tue, 31 May 2022 15:18:16 -0000

Hi All,

I have created a thin LVM on top the existing *data* thin pool, as follows:

lvcreate -V2T -T pve/data -n vms

The resulting *vms* LVM is a thin LVM volume which then I format and mount
it at boot.
I perform this so as to be able to setup a gluster setup with three nodes
where the bricks will resize in the mountpoint of the thin LVM volume.

I have observed that when the hosts boot randomly, perhaps after a power
cut, they might temporarily lose quorum, which is expected until the nodes
are booted and the quorum is met. On loss of the quorum the mount point of
the thin LVM I have created is not able to mount and I suspect that this is
due to Proxmox not enabling the data thin pool if quorum is not met.

Is this the case? Can someone confirm this or provide any idea/hint what
could be wrong with this approach? I was thinking of checking if creating
the thin LVM on top of a different pool and volume group that Proxmox does
not manage might resolve the issue.

Thanx,
Alex