public inbox for pve-user@lists.proxmox.com
 help / color / mirror / Atom feed
From: "Óscar de Arriba" <oscar@dearriba.es>
To: "Alain Péan" <alain.pean@c2n.upsaclay.fr>,
	"Proxmox VE user list" <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] Thin LVM showing more used space than expected
Date: Wed, 28 Dec 2022 19:22:52 +0100	[thread overview]
Message-ID: <4720409e-c9f6-442d-b6c6-0e2f006c4b17@app.fastmail.com> (raw)
In-Reply-To: <8f8156db-ec51-a426-3146-3fcf843b5699@c2n.upsaclay.fr>

> I saw that they are Crucial SATA SSD directly attached on the motherboard. What kind of filesystem do you have on these SSDs ? Can you run pveperf on /dev/mapper/pveroot to see what are the performances ?

It is using LVM with ext4 for the root filesystem and the data storage is using LVM-Thin.

root@venom:~# blkid
/dev/sdj2: UUID="7B86-9E58" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="f4324ec9-c95e-4963-9ea9-5026f8f3fcae"
/dev/sdj3: UUID="16ioTj-mei2-pqZI-bJWU-myRs-AF5a-Pfw03x" TYPE="LVM2_member" PARTUUID="d2528e8f-7958-4dc1-9960-f67999b75058"
/dev/mapper/pve-swap: UUID="0fbe15d8-7823-42bc-891c-c131407921c7" TYPE="swap"
/dev/mapper/pve-root: UUID="6bef8c06-b480-409c-8fa0-076344c9108d" BLOCK_SIZE="4096" TYPE="ext4"
/dev/sdj1: PARTUUID="70bb576f-ab3a-4867-ab2e-e9a7c3fb5a15"
/dev/mapper/pve-vm--150--disk--1: PTUUID="90e3bde4-d85c-46cb-a4b9-799c99e340c6" PTTYPE="gpt"
/dev/mapper/pve-vm--201--disk--1: PTUUID="cb44eeb1-db0d-4d42-8a14-05077231b097" PTTYPE="gpt"

root@venom:~# lvs
  LV            VG  Attr       LSize   Pool Origin Data%  Meta%  Move Log Cpy%Sync Convert
  data          pve twi-aotz-- 377.55g             96.60  1.55                            
  root          pve -wi-ao----  60.00g                                                    
  swap          pve -wi-ao----   4.00g                                                    
  vm-150-disk-0 pve Vwi-a-tz--   4.00m data        14.06                                  
  vm-150-disk-1 pve Vwi-a-tz-- 128.00g data        100.00                                 
  vm-201-disk-0 pve Vwi-aotz--   4.00m data        14.06                                  
  vm-201-disk-1 pve Vwi-aotz--  40.00g data        75.89

Regarding pveperf:

root@venom:~# pveperf /dev/mapper/pve-root
CPU BOGOMIPS:      211008.96
REGEX/SECOND:      1983864
HD SIZE:           58.76 GB (/dev/mapper/pve-root)
BUFFERED READS:    338.10 MB/sec
AVERAGE SEEK TIME: 0.09 ms
open failed: Not a directory

root@venom:~# pveperf ~/
CPU BOGOMIPS:      211008.96
REGEX/SECOND:      2067874
HD SIZE:           58.76 GB (/dev/mapper/pve-root)
BUFFERED READS:    337.51 MB/sec
AVERAGE SEEK TIME: 0.09 ms
FSYNCS/SECOND:     679.87
DNS EXT:           128.22 ms
DNS INT:           127.51 ms

Thanks,
Oscar


  reply	other threads:[~2022-12-28 18:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-27 17:54 Óscar de Arriba
2022-12-28 10:52 ` Alain Péan
2022-12-28 11:19   ` Óscar de Arriba
2022-12-28 12:17     ` Alain Péan
2022-12-28 18:22       ` Óscar de Arriba [this message]
     [not found] <mailman.3.1672225201.17323.pve-user@lists.proxmox.com>
2022-12-28 11:44 ` Óscar de Arriba
     [not found]   ` <b462e244-86a1-eada-c50b-4361f037dc1e@holub.co.at>
2022-12-29 10:48     ` Óscar de Arriba
2022-12-29 16:58       ` Óscar de Arriba
2022-12-30  9:52         ` Tom Weber
2023-01-02  9:56         ` Óscar de Arriba

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4720409e-c9f6-442d-b6c6-0e2f006c4b17@app.fastmail.com \
    --to=oscar@dearriba.es \
    --cc=alain.pean@c2n.upsaclay.fr \
    --cc=pve-user@lists.proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal