Weird LV Misunderstanding. Re-occurring bad superblocks. Probably bad setup.

rsvg

New Member
Mar 23, 2021
20
0
1
41
So, I believe I have a fundamental mistake in my setup, and I'm really hoping someone can help me resolve it because I'm definitely new, and having a rough time figuring out the "proper" way to store data in proxmox.

I initially set up this host with a manual install of proxmox on debian because I need a new version of ZFS.

The issue starts when I restored a VM from a backup, and it wouldn't boot because the filesystem wouldn't mount, so I repaired it with "fsck -b", and got it to run.

The bigger problem is that shortly after that, I reboot the host, and now my pve-data LV has a bad superblock, and cannot be mounted. I figure this is because i "fixed" the file system of the VM that is stored on data.

So I comment that line out in the /etc/fstab.

Code:
#/dev/mapper/pve-data /var/lib/vz     ext4    discard,noatime,nodiratime 0       2

After that the host boots, and I can still see the data in the proxmox gui, acts like everything is fine even though it isn't mounted at /var/lib/vz. This confuses me even more, also my VM again cannot mount it's root FS.

So, I have no idea where to go from here, all I want is a "data" file system on the same NVME that root is on so proxmox can use to host VMs on without them being corrupted somehow. I'd really appreciate any help with this.

Here are all my outputs/setup:

fdisk -l

Code:
Disk /dev/nvme0n1: 1.5 TiB, 1600321314816 bytes, 3125627568 sectors
Disk model: SAMSUNG MZWLL1T6HAJQ-00005
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 17291F4A-4E34-42A5-8487-3F0FAF5395EF

Device           Start        End    Sectors  Size Type
/dev/nvme0n1p1    2048    1050623    1048576  512M EFI System
/dev/nvme0n1p2 1050624 3125626879 3124576256  1.5T Linux LVM


Disk /dev/mapper/pve-root: 882.2 GiB, 947216449536 bytes, 1850032128 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mapper/pve-swap: 7.5 GiB, 7998537728 bytes, 15622144 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mapper/pve-vm--101--disk--0: 32 GiB, 34359738368 bytes, 67108864 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 131072 bytes / 262144 bytes
Disklabel type: gpt
Disk identifier: 68BFC9CD-489D-4BCE-AAED-BE394C38E57F

Device                                 Start      End  Sectors Size Type
/dev/mapper/pve-vm--101--disk--0-part1  2048     4095     2048   1M BIOS boot
/dev/mapper/pve-vm--101--disk--0-part2  4096 67106815 67102720  32G Linux filesystem


GPT PMBR size mismatch (1258291199 != 25165823) will be corrected by write.
The primary GPT table is corrupt, but the backup appears OK, so that will be used.
Disk /dev/mapper/pve-vm--100--disk--0: 12 GiB, 12884901888 bytes, 25165824 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 131072 bytes / 262144 bytes
Disklabel type: gpt
Disk identifier: A5728BE8-5F8C-40B4-919F-1AC4B62868CE

Device                                 Start      End  Sectors Size Type
/dev/mapper/pve-vm--100--disk--0-part1  2048     4095     2048   1M BIOS boot
/dev/mapper/pve-vm--100--disk--0-part2  4096 25163775 25159680  12G Linux filesystem


Disk /dev/mapper/pve-vm--102--disk--0: 32 GiB, 34359738368 bytes, 67108864 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 131072 bytes / 262144 bytes

lvdisplay

Code:
--- Logical volume ---
  LV Path                /dev/pve/root
  LV Name                root
  VG Name                pve
  LV UUID                FBnvgB-7Wu0-nY6c-iEhG-HQov-DruK-UyHRCw
  LV Write Access        read/write
  LV Creation host, time palm, 2021-04-04 18:03:33 -0500
  LV Status              available
  # open                 1
  LV Size                882.16 GiB
  Current LE             225834
  Segments               2
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:0

  --- Logical volume ---
  LV Path                /dev/pve/swap
  LV Name                swap
  VG Name                pve
  LV UUID                scNNKf-hZhE-rQ13-wpkC-QjXe-4AqK-mHGJY7
  LV Write Access        read/write
  LV Creation host, time palm, 2021-04-04 18:03:46 -0500
  LV Status              available
  # open                 2
  LV Size                <7.45 GiB
  Current LE             1907
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:1

  --- Logical volume ---
  LV Name                data
  VG Name                pve
  LV UUID                27nhKq-fmER-KHSH-W7Cw-ebaN-dlQ1-Faxy2X
  LV Write Access        read/write
  LV Creation host, time palm, 2021-04-12 18:00:02 -0500
  LV Pool metadata       data_tmeta
  LV Pool data           data_tdata
  LV Status              available
  # open                 4
  LV Size                600.00 GiB
  Allocated pool data    6.79%
  Allocated metadata     13.85%
  Current LE             153600
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:4

  --- Logical volume ---
  LV Path                /dev/pve/vm-101-disk-0
  LV Name                vm-101-disk-0
  VG Name                pve
  LV UUID                x28xyt-3byX-7SMt-GIiE-pdVo-WwAj-lcQxME
  LV Write Access        read/write
  LV Creation host, time palm, 2021-04-12 19:48:23 -0500
  LV Pool name           data
  LV Status              available
  # open                 0
  LV Size                32.00 GiB
  Mapped size            97.13%
  Current LE             8192
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:6

  --- Logical volume ---
  LV Path                /dev/pve/vm-100-disk-0
  LV Name                vm-100-disk-0
  VG Name                pve
  LV UUID                4cxppO-G0iT-XGEC-rtph-WcFs-jvx4-32FWYG
  LV Write Access        read/write
  LV Creation host, time palm, 2021-04-12 19:57:28 -0500
  LV Pool name           data
  LV Status              available
  # open                 1
  LV Size                12.00 GiB
  Mapped size            80.26%
  Current LE             3072
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:7

  --- Logical volume ---
  LV Path                /dev/pve/vm-102-disk-0
  LV Name                vm-102-disk-0
  VG Name                pve
  LV UUID                Ncjfjl-YwYH-sQuR-8CY3-HFra-d8XT-opsToE
  LV Write Access        read/write
  LV Creation host, time palm, 2021-04-15 10:44:18 -0500
  LV Pool name           data
  LV Status              available
  # open                 0
  LV Size                32.00 GiB
  Mapped size            0.00%
  Current LE             8192
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:8

vgdisplay

Code:
  --- Volume group ---
  VG Name               pve
  System ID
  Format                lvm2
  Metadata Areas        1
  Metadata Sequence No  89
  VG Access             read/write
  VG Status             resizable
  MAX LV                0
  Cur LV                6
  Open LV               3
  Max PV                0
  Cur PV                1
  Act PV                1
  VG Size               1.45 TiB
  PE Size               4.00 MiB
  Total PE              381417
  Alloc PE / Size       381417 / 1.45 TiB
  Free  PE / Size       0 / 0
  VG UUID               eP9fE0-s7Wn-eitV-CQtn-Fx3a-1Y89-GNBz2H

Code:
Filesystem            Size  Used Avail Use% Mounted on
udev                   16G     0   16G   0% /dev
tmpfs                 3.2G  9.9M  3.1G   1% /run
/dev/mapper/pve-root  869G   33G  801G   4% /
tmpfs                  16G   66M   16G   1% /dev/shm
tmpfs                 5.0M     0  5.0M   0% /run/lock
tmpfs                  16G     0   16G   0% /sys/fs/cgroup
/dev/nvme0n1p1        511M  5.2M  506M   2% /boot/efi
/dev/fuse              30M   24K   30M   1% /etc/pve
tmpfs                 3.2G     0  3.2G   0% /run/user/1000
 
And even more than help, I'm looking for the fundamentals of how this Data LV is supposed to work with proxmox.

Is it just an LV?

Do you create a file system on it?

Are we supposed to mount /dev/pve/data at /var/lib/vz?

If I don't mount it, how is it showing as fine in proxmox and I can still create a VM on it as if it's working properly?
 
Last edited:
Also, if I do fdisk on the LV itself it says it's only 12G?!

Code:
╰─○ sudo fdisk -l /dev/mapper/pve-data
Disk /dev/mapper/pve-data: 600 GiB, 644245094400 bytes, 1258291200 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 131072 bytes / 262144 bytes
Disklabel type: gpt
Disk identifier: A5728BE8-5F8C-40B4-919F-1AC4B62868CE

Device                     Start      End  Sectors Size Type
/dev/mapper/pve-data-part1  2048     4095     2048   1M BIOS boot
/dev/mapper/pve-data-part2  4096 25163775 25159680  12G Linux filesystem
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!