[SOLVED] LVM auf durchgereichten Festplatten -> Fehler am Host

der-brumm-baer

New Member
Aug 22, 2018
7
1
3
40
Hallo,

Ich betreibe auf meinem Proxmox Server einen Openmediavault Filserver.
Hierfür habe ich einen SATA Controller an das virtuelle KVM-System durchgereicht.
Die daran angeschlossenen Festplatten sind auch mittels LVM partitioniert.

Jetzt habe ich das Problem, dass die Volumes auf diesen Platten auch im vgscan des Host
auftauchen, aber eben als fehlende Partitionen
Ausgabe von vgscan:
Code:
  Reading all physical volumes.  This may take a while...
  /dev/vg_daten010/lv_daten011: read failed after 0 of 4096 at 0: Input/output error
  /dev/vg_daten010/lv_daten011: read failed after 0 of 4096 at 2000162848768: Input/output error
  /dev/vg_daten010/lv_daten011: read failed after 0 of 4096 at 2000162906112: Input/output error
  /dev/vg_daten010/lv_daten011: read failed after 0 of 4096 at 4096: Input/output error
  /dev/vg_daten010/lv_daten012: read failed after 0 of 4096 at 0: Input/output error
  /dev/vg_daten010/lv_daten012: read failed after 0 of 4096 at 2000162848768: Input/output error
  /dev/vg_daten010/lv_daten012: read failed after 0 of 4096 at 2000162906112: Input/output error
  /dev/vg_daten010/lv_daten012: read failed after 0 of 4096 at 4096: Input/output error
  /dev/vg_daten010/lv_daten013: read failed after 0 of 4096 at 0: Input/output error
  /dev/vg_daten010/lv_daten013: read failed after 0 of 4096 at 2000162848768: Input/output error
  /dev/vg_daten010/lv_daten013: read failed after 0 of 4096 at 2000162906112: Input/output error
  /dev/vg_daten010/lv_daten013: read failed after 0 of 4096 at 4096: Input/output error
  /dev/vg_daten010/lv_daten014: read failed after 0 of 4096 at 0: Input/output error
  /dev/vg_daten010/lv_daten014: read failed after 0 of 4096 at 2000162848768: Input/output error
  /dev/vg_daten010/lv_daten014: read failed after 0 of 4096 at 2000162906112: Input/output error
  /dev/vg_daten010/lv_daten014: read failed after 0 of 4096 at 4096: Input/output error
  /dev/vg_daten010/lv_daten015: read failed after 0 of 4096 at 0: Input/output error
  /dev/vg_daten010/lv_daten015: read failed after 0 of 4096 at 2000162848768: Input/output error
  /dev/vg_daten010/lv_daten015: read failed after 0 of 4096 at 2000162906112: Input/output error
  /dev/vg_daten010/lv_daten015: read failed after 0 of 4096 at 4096: Input/output error
  /dev/vg_daten030/lv_daten031: read failed after 0 of 4096 at 0: Input/output error
  /dev/vg_daten030/lv_daten031: read failed after 0 of 4096 at 2003321159680: Input/output error
  /dev/vg_daten030/lv_daten031: read failed after 0 of 4096 at 2003321217024: Input/output error
  /dev/vg_daten030/lv_daten031: read failed after 0 of 4096 at 4096: Input/output error
  /dev/vg_daten030/lv_daten032: read failed after 0 of 4096 at 0: Input/output error
  /dev/vg_daten030/lv_daten032: read failed after 0 of 4096 at 1997461716992: Input/output error
  /dev/vg_daten030/lv_daten032: read failed after 0 of 4096 at 1997461774336: Input/output error
  /dev/vg_daten030/lv_daten032: read failed after 0 of 4096 at 4096: Input/output error
  Found volume group "pve" using metadata type lvm2
Jetzt habe ich schon versucht, in der /etc/lvm/lvm.conf einen Filter zu setzen, doch das
scheint nicht zu wirken:
Code:
      # Example
        # Accept every block device:
        # filter = [ "a|.*/|" ]
        # Reject the cdrom drive:
        # filter = [ "r|/dev/cdrom|" ]
        # Work with just loopback devices, e.g. for testing:
        # filter = [ "a|loop|", "r|.*|" ]
        # Accept all loop devices and ide drives except hdc:
        # filter = [ "a|loop|", "r|/dev/hdc|", "a|/dev/ide|", "r|.*|" ]
        # Use anchors to be very specific:
        # filter = [ "a|^/dev/hda8$|", "r|.*/|" ]
        #
        # This configuration option has an automatic default value.
        # filter = [ "a|.*/|" ]
        filter = [ "r|/dev/sdb|", "r|/dev/sdc|" ]
Mit dmesg und im syslog taucht auch laufend folgende Fehlermeldung auf:

dmesg:
Code:
[58646.459708] blk_partition_remap: fail for partition 1
syslog:
Code:
pve kernel: [58656.623222] blk_partition_remap: fail for partition 1
Wie kann ich die Festplatten vom Scan in LVM ausschliessen?

MfG
Sven
 

der-brumm-baer

New Member
Aug 22, 2018
7
1
3
40
Hallo,

habe es jetzt hinbekommen.

Zusätzlich habe ich noch den "global_filter" um die Anfangsbuchstaben des Namens der VolumeGroup
erweitert. ( , "r|/dev/mapper/vg.*|")

Code:
        # Do not scan ZFS zvols (to avoid problems on ZFS zvols snapshots)
        global_filter = [ "r|/dev/zd.*|", "r|/dev/mapper/pve-.*|" , "r|/dev/mapper/vg.*|"]

        # Example
        # Accept every block device:
        # filter = [ "a|.*/|" ]
        # Reject the cdrom drive:
        # filter = [ "r|/dev/cdrom|" ]
        # Work with just loopback devices, e.g. for testing:
        # filter = [ "a|loop|", "r|.*|" ]
        # Accept all loop devices and ide drives except hdc:
        # filter = [ "a|loop|", "r|/dev/hdc|", "a|/dev/ide|", "r|.*|" ]
        # Use anchors to be very specific:
        # filter = [ "a|^/dev/hda8$|", "r|.*/|" ]
        #
        # This configuration option has an automatic default value.
        # filter = [ "a|.*/|" ]
        filter = [ "r|/dev/sdb|", "r|/dev/sdc|" ]
der lvscan ist jetzt sauber, und die Fehler im dmesg und syslog sind auch verschwunden.

MfG
Sven
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE 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 your own in 60 seconds.

Buy now!