iSCSI - only LUN shown, can't format/use LVM or ext4

Discussion in 'Proxmox VE: Installation and configuration' started by ivdok, Jun 21, 2019.

  1. ivdok

    ivdok New Member

    Joined:
    Mar 12, 2019
    Messages:
    7
    Likes Received:
    0
    Code:
    pveversion --verbose
    proxmox-ve: 5.4-1 (running kernel: 4.15.18-16-pve)
    pve-manager: 5.4-6 (running version: 5.4-6/aa7856c5)
    pve-kernel-4.15: 5.4-4
    pve-kernel-4.15.18-16-pve: 4.15.18-41
    pve-kernel-4.15.18-15-pve: 4.15.18-40
    pve-kernel-4.15.18-14-pve: 4.15.18-39
    pve-kernel-4.15.18-13-pve: 4.15.18-37
    pve-kernel-4.15.18-12-pve: 4.15.18-36
    pve-kernel-4.15.18-9-pve: 4.15.18-30
    ceph: 12.2.12-pve1
    corosync: 2.4.4-pve1
    criu: 2.11.1-1~bpo90
    glusterfs-client: 3.8.8-1
    ksm-control-daemon: 1.2-2
    libjs-extjs: 6.0.1-2
    libpve-access-control: 5.1-10
    libpve-apiclient-perl: 2.0-5
    libpve-common-perl: 5.0-52
    libpve-guest-common-perl: 2.0-20
    libpve-http-server-perl: 2.0-13
    libpve-storage-perl: 5.0-43
    libqb0: 1.0.3-1~bpo9
    lvm2: 2.02.168-pve6
    lxc-pve: 3.1.0-3
    lxcfs: 3.0.3-pve1
    novnc-pve: 1.0.0-3
    proxmox-widget-toolkit: 1.0-28
    pve-cluster: 5.0-37
    pve-container: 2.0-39
    pve-docs: 5.4-2
    pve-edk2-firmware: 1.20190312-1
    pve-firewall: 3.0-22
    pve-firmware: 2.0-6
    pve-ha-manager: 2.0-9
    pve-i18n: 1.1-4
    pve-libspice-server1: 0.14.1-2
    pve-qemu-kvm: 3.0.1-2
    pve-xtermjs: 3.12.0-1
    qemu-server: 5.0-52
    smartmontools: 6.5+svn4324-1
    spiceterm: 3.0-5
    vncterm: 1.5-3
    zfsutils-linux: 0.7.13-pve1~bpo2
    
    Code:
    cat /etc/pve/storage.cfg
    dir: local
       path /var/lib/vz
       content vztmpl,iso,backup
       maxfiles 31
       shared 0
    
    zfspool: local-zfs
       pool rpool/data
       content images,rootdir
       sparse 1
    
    iscsi: iscsi
       portal 172.26.1.2
       target iqn.1991-05.com.microsoft:hv-target-target
       content none
       nodes prod-4,prod-3,prod-2
    
    All I see after connecting to iSCSI target is a raw LUN which I can't do shit with - it's unremovable from storage, unformattable within GUI, nothing can be added to the storage, and putting LVM over it does nothing too. Of course I can mount it via fstab as a directory and be done with it, but shouldn't anything in GUI be "production-ready"?
     

    Attached Files:

  2. dcsapak

    dcsapak Proxmox Staff Member
    Staff Member

    Joined:
    Feb 1, 2016
    Messages:
    3,611
    Likes Received:
    328
    what do you mean by this?

    normally you now add an 'LVM' storage with your iscsi storage as base and then use your lvm storage for the vms
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. ivdok

    ivdok New Member

    Joined:
    Mar 12, 2019
    Messages:
    7
    Likes Received:
    0
    Everything is greyed out, no option to transfer backup/vm or even upload ISO, even with cfg tweak:
    Code:
    lvm: test
            vgname vg0
            base ext4:0.0.0.scsi-360003ff44dc75adcb2086df0c62928fa
            content rootdir,images,backup,iso,vztmpl
            shared 1
    
    And iSCSI storage is left hanging in storage list, with no use other than being an eyesore.
     
  4. dcsapak

    dcsapak Proxmox Staff Member
    Staff Member

    Joined:
    Feb 1, 2016
    Messages:
    3,611
    Likes Received:
    328
    lvm is a block storage, you cannot store files there only ct/vm images so this is no suprise

    to store isos/backups/ct templates you need a file based storage, such as a local directory/nfs/smb/etc.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. ivdok

    ivdok New Member

    Joined:
    Mar 12, 2019
    Messages:
    7
    Likes Received:
    0
    I've tried to create ext4 on top of LVM on top of iSCSI block, and then mounting in FS and making it a shared "folder" type storage in PVE, but it doesn't sync anything between the nodes. Flushing manually with "sync; sync; sync" doesn't affect anything either.
     
  6. Stoiko Ivanov

    Stoiko Ivanov Proxmox Staff Member
    Staff Member

    Joined:
    May 2, 2018
    Messages:
    1,269
    Likes Received:
    117
    ext4 will not work for this - you would need a cluster filesystem (ocfs, gfs2) for this - otherwise you can only mount the lvm on one host (or you'll get a filesystem corruption when 2 writers write to it) - maybe your storage supports NFS, and you can mount a share on all your nodes?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice