Search results

I am having a problem creating a udev rule that sets max_sectors_kb to 1024 for sd* (sda,sdb,sdc etc...) devices under /sys/block/. Specifically, a recent kernel change means the max IO is too large for my iSCSI SAN so I am trying to set it to 1024 on startup. I have tried the following from...

I have come across this and can confirm the calculation issue is still present in PVE 4.2. https://forum.proxmox.com/threads/iscsi-issues-dell-compellent-san-corruption-of-superblocks-and-controllers.17999/page-2#post-141470

I have just tested the iscsi initiator in windows server 2012 and it has no problems using the LUN's at all.

I am using a HP P2000 G3 10Gbit iSCSI SAN. This same unit worked fine on PVE 3.3. I don't believe that I can configure those limits. The errors occur as soon as a VM tries to partition the disk upon OS installation.

Oh, well any ideas why I might be suffering exactly the same symptoms? I followed the iSCSI MPIO guide to a tee and this is not the first time I have configured iSCSI with MPIO anyway... I had it working on PVE 3.3 absolutely fine. Logs are full of this for any LUN I use: Jul 28 09:00:17...

Anyone? Nothing I do is getting iSCSI working. After anything starts writing, I get failures.

I appear to be suffering from the same issue with a new 16 node cluster in PVE 4.2. Is this a confirmed issue?

I have been spending the last 2 days trying to work out why I cannot restore or create any VM's onto my iSCSI backed LVM storage on a brand new 16 node Proxmox VE 4.2 cluster. The nodes are able to create logical volumes in the volume groups however when data starts writing, things grind to a...

Ok, I CANNOT create new VM's either. The logical volume appears to create, but any writing to it such as partition table, fails.

The target storage is iSCSI backed LVM. MPIO configured. There is more than enough space on any of the target LUN's I try and use. This is a new cluster so I havn't even tried to make a new VM, I will try that later today. Any ideas?

Hi guys, I am trying to restore a VM from a USB drive via the command line and have run into an issue. The restore fails with exit code 133 every time. My target storage is LVM backed with iSCSI, plenty of space. However, it appears that qmrestore tries to use /var/tmp as the location to...

I got excited about using ZFS on my ISCSI LUN's until I read that it does not work as a clustered file system so I would be unable to share the storage across hosts and use live migration. The wiki also says multipath devices not supported with ZFS.

I have noticed this as well with 4.2, can't say I really did any big restores on 3.x. Several large restores on 4.2 cause the whole host and every VM on it to become extremely slow and even not responsive at all. The host isn't a powerhouse but its still a dual quad opteron with 64G of RAM...

Hi guys, Just think having iSCSI MPIO configuration options in the GUI for cluster wide MPIO configuration would be a good idea. Saves having to create an MPIO configuration on every cluster node then present it for LVM in GUI. Tom

What I would like to see is the IP address of VM's pulled from the qemu agent and displayed in the GUI :-)

Splitting a cluster out over a 'WAN' is typically not good practice. A cluster is supposed to describe a local entity, a group of hosts in the same rack/row/datahall for example. Cluster & storage networking is paramount to the performance of the cluster and therefore local networking for your...

Thanks, that means with any luck, 4.2 might have been released just in time for my move.

Hi there, I am about to carry out a major datacentre migration and during that time, an upgrade of our proxmox cluster. I have just seen that new packages have made their way into pvetest including 4.4 kernel and new GUI. Whats the timeframe for full release? Will it be out within the next...

So it seems like the only option if I want to use QCOW2 snapshots is to serve the iSCSI LUNS up to a 'gateway' server of some sort, then kick it out to Proxmox as NFS? Doesn't seem worth compromising the integrity of my storage subsystem just for the sake of snapshots if im honest....

Hi there, I am about to perform a restructure of our virtual environment and as such upgrade to 4.1. I currently present iSCSI to 16 servers, have a multipath device configured and LVM on top of that. Obviously I can't have snapshots on LVM since it required RAW VM disks. I just wondered if...