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 39004723CB for ; Mon, 12 Apr 2021 13:13:38 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 1D2921DF2A for ; Mon, 12 Apr 2021 13:13:08 +0200 (CEST) Received: from mail-lj1-x233.google.com (mail-lj1-x233.google.com [IPv6:2a00:1450:4864:20::233]) (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 38CE61DF16 for ; Mon, 12 Apr 2021 13:13:06 +0200 (CEST) Received: by mail-lj1-x233.google.com with SMTP id u4so14857157ljo.6 for ; Mon, 12 Apr 2021 04:13:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tecnetmza-com-ar.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=3uJeNhsN7f7GnEs0tdWuhc0b+msmmGBMsLl/45CiO/0=; b=vNZ2/4gBBFPGpTMmooGzyIxE3+r/WhzFaq4hP+IHQZWkSRVpB5dOLbxSyEtDr/F9lA u2FWw4ti17aF4FhzCSlSbmvCnBqRwjSTMyv9QaTDxfztI7cgxFtjXoyqrthvNuo1mnSn KhtLSyRX9MPG7n5w70/Tr2En4EMTlGEg+9k6LQyg6EdecJTp1x+G55LZp2Wgl1kgpJ/Q j6IO2qHZCdcyut6RETd7D+uV30TyEEWJzlpp+T4qM58knnKLSEUblgRARivP3t7WpGRn IWIthDSybA5r6/abtLn5tqN3V0cAiKhjiMOuKsJ7k6RXXtvW+0OjYVCrQwP+Ka9n2O+Z QqXQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=3uJeNhsN7f7GnEs0tdWuhc0b+msmmGBMsLl/45CiO/0=; b=KNph5KXt3DYAkenA+sbMSpSjRF96ueatpTtwBlFPZW38URIgsy2bOVSfdjvRCjDcM8 SLkCOjlHdZGoY90rEjquKTNmy0a9KfA5r79qMbgLuyQiCYcEPz2AWsVGg/iVfJiYADQs NvXo0uB2wglu0Q0RdUoK5vjrwHCH8lQYF1LvMCiiOPiLzPzzRIUOCn8yCLxXhfUU0O9C 7GAXa6wAFYEDu2Gx6GlT9oKvZ6Nl9900wkwQQ3JYvsMHwIaSEaEE5cJ0TLV8d8Fe/2FK SqHJH8ppZVsAW0Y01PTJ+HZLBzSQ633us0rUy5hpeXqto7RjbOwVGpXj0PjNc6YD+/d6 WhRw== X-Gm-Message-State: AOAM531ybc5e9V2IrZ1GfiSAbP5kneKTtxV+i+v3YC6i4jd2tfbFtwRR c8Te8gAo5LO1IA1T/83aR019U6GHthUyNobYU0XegRZY1g== X-Google-Smtp-Source: ABdhPJx91qGUHqly0xjTNN2+gdgdBx5e1EQ3p3ayv1yKSRTsrzbPMY1CNs6yzBgucYZX6pU6gA5WLYn78W5CN4a47cQ= X-Received: by 2002:a2e:6c06:: with SMTP id h6mr18100849ljc.154.1618225979610; Mon, 12 Apr 2021 04:12:59 -0700 (PDT) MIME-Version: 1.0 References: <2509fa63-a5b2-658a-610f-0497202d2f6f@proxmox.com> In-Reply-To: <2509fa63-a5b2-658a-610f-0497202d2f6f@proxmox.com> From: Leandro Roggerone Date: Mon, 12 Apr 2021 08:12:48 -0300 Message-ID: To: Dominik Csapak , PVE User List X-SPAM-LEVEL: Spam detection results: 1 AWL 0.189 Adjusted score from AWL reputation of From: address 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 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_SOFTFAIL 0.972 SPF: sender does not match SPF record (softfail) T_REMOTE_IMAGE 0.01 Message contains an external image Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 Subject: Re: [PVE-User] LVM question 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: Mon, 12 Apr 2021 11:13:38 -0000 Thanks !! very helpful. Libre de virus. www.avast.com <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> El lun, 12 abr 2021 a las 3:48, Dominik Csapak () escribi=C3=B3: > Hi, > > On 4/9/21 19:19, Leandro Roggerone wrote: > > Hi guys , after install a new storage to my box , had to create lvm-thi= n. > > Im not very good with lvm , after reading some docs , and links like: > > > https://forum.proxmox.com/threads/how-to-create-an-lvm-thinpool-and-vz-di= rectory-on-the-same-disk.62901/ > > > > I got a working solution but have also some questions about it. > > This is what I did: > > > > wipefs -a /dev/sdb > > > > sgdisk -N 1 /dev/sdb > > > > pvcreate --metadatasize 1024M -y -ff /dev/sdb1 > > > > vgcreate --metadatasize 1024M proxvg /dev/sdb1 > > > > lvcreate -l 100%FREE --poolmetadatasize 1024M --chunksize 256 -T -n > > proxthin proxvg > > > > lvcreate -n proxvz -V 1.1T proxvg/proxthin > > > > mkfs.ext4 /dev/proxvg/proxvz > > > > mkdir /media/vz > > > > echo '/dev/proxvg/proxvz /media/vz ext4 defaults,errors=3Dremount-ro 0 = 2' > >> > > /etc/fstab > > > > mount -a > > > > > > And have following result: > > > > > > root@pve2:~# lvs > > LV VG Attr LSize Pool Origin Data% Meta= % > > Move Log Cpy%Sync Convert > > proxthin proxvg twi-aotz-- 1.63t 22.03 6.34 > > > > proxvz proxvg Vwi-aotz-- 1.10t proxthin 1.67 > > root@pve2:~# lvdisplay > > --- Logical volume --- > > LV Name proxthin > > VG Name proxvg > > LV UUID 4cEIr9-3ZVQ-vsy1-q9ZX-GsaD-7oq0-pZixsX > > LV Write Access read/write > > LV Creation host, time pve2, 2021-04-01 13:09:41 -0300 > > LV Pool metadata proxthin_tmeta > > LV Pool data proxthin_tdata > > LV Status available > > # open 3 > > LV Size 1.63 TiB > > Allocated pool data 22.03% > > Allocated metadata 6.34% > > Current LE 428451 > > Segments 1 > > Allocation inherit > > Read ahead sectors auto > > - currently set to 256 > > Block device 253:2 > > > > --- Logical volume --- > > LV Path /dev/proxvg/proxvz > > LV Name proxvz > > VG Name proxvg > > LV UUID huzpPT-g0Gd-3Jwb-2ydz-InHh-73vN-Jnc5TR > > LV Write Access read/write > > LV Creation host, time pve2, 2021-04-01 13:10:12 -0300 > > LV Pool name proxthin > > LV Status available > > # open 1 > > LV Size 1.10 TiB > > Mapped size 1.67% > > Current LE 288359 > > Segments 1 > > Allocation inherit > > Read ahead sectors auto > > - currently set to 256 > > Block device 253:4 > > > > > > Have following comments: > > > > I can create VMs on proxthin partition so it is ok. > > > > I can create backup on proxvz partition so it is ok. > > Looks OK imho. > > > > > What im concerned about is: > > > > Physic storage space is about 1.8TG , how is it possible to create a 1.= 6 > > and 1.1T volumnes inside ? > > LVM Thin is 'thin-provisioned' it only uses space when it is really > written. > > > It can be a problem in the future ? > > yes, if you do not monitor your real usage, if the thinpool runs full, > you can lose data. > > > I was thinking about reduce proxthin partition to 600Gb aprox , so it > make > > same sense 1.1T + 600G aprox 1.8 T > > But there is no LV Path on proxthin partition so I can unmount and the > > reduce. > > So .. > > What im missing here ? do I need to reduce proxthin partition ( I do ne= ed > > the 1.1T partition to backup). > > the LV 'proxvz' is inside the thinpool 'proxthin' so as long as you > never allocate more that ~500GiB of vm/ct volumes, it should be fine. > > alos, on allocation, the thinpool will print warnings if the allocated > lvs are bigger than the space available > > hope this helps > > > Hope to be clear about this guys. > > Any comment would be wellcome. > > Leandro. > > _______________________________________________ > > pve-user mailing list > > pve-user@lists.proxmox.com > > https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user > > > > > > >