Search results

Enlarging the PV while the logical volumes should work, but I would advise you to test this on a test storage. Procedure is more or less as such: * enlarge the LUN on your SAN * rescan the iscsi targets on the PVE host iscsiadm --mode session --rescan * check with lsblk that the linux block...

@SilverNodashi out of curiosity which tool do you use for measuring that ? ioping ?

First be aware that PVE is not meant to be use as a jack-of-all-trade-can-do-everything server, but a Virtualization host, so your question is a bit out of topic. We actually do not encourage adding extra services like a NFS server on a Proxmox host. Now for debugging the nfs-kernel-servers...

What volume do you want to extend with pvresize ?

Well I am new to FC too :) My understanding of FC controllers, is that they will present you a list of block devices. So if PVE sees the card, check with lsscsi ( apt install lsscsi) and lsblk if you see the disks exported from the SAN.

Try the following command: lspci | grep "Fibre Channel" It will show you a list of HBA FC controllers on your PCI bus Then try lspci -k | sed -n '/Fibre Channel/,/Kernel modules/p' this will show you detailed information about the FC HBA, including the kernel driver in use

@hellowordl: thank you very much for your feedback. We cannot possibily test all virtualization use cases, so it is important to here when something which was not working is now fine when applying the proposed fix. Marking this as solved.

looks at this: cache 104G I think this is what is causing your problem whenever the kernel flushes this tremendous cache on your SAS drives (well not of all) all other IO will be blocked you do not need to reduce the RAM of your server, you just need to ask him to cache a little bit less so...

"Guest has not initialized the display yes" is an very early boot error of the VMs and can have a number of different cause. As it happens very early during the boot sequence it is usually not possible to do a proper shutdown, either via ACPI or guest-agent. Did the machines started after they...

Up to now we covered the most common use case, that the PVE bridge vmbr0 is connected to a switch where is receives the proper VLAN tags, and when creating a VM NIC you just need to specify one of those VLAN tags. Can you please explain what is your use case in details ?

this message from pvesm status is just a warning and not an error probably you created a LVM PV on this LUN, but since you exported this LUN via multiple paths, the PV signature is found on multiple disks normally if you export a LUN via multiple paths, you would use a multipath daemon on the...

this looks to me like a iscsi connectivity problem the LUNs exposed from your SAN are not available, hence the kernel cannot perform IO on the associated bloc device verify if your iscsi session is still active with: iscsiadm -m session -P 2 you should be logged in and active

The documentation you quote is about snapshotting and thin provisioning. Discarding unuseed blocks is a different topic. Also your test is detailed enough because in all you tests we see 1,1 GB size on host :)

which command are you using to restart the container ? pct start / pct stop ? there is no reason it should not be working on the console and note in the GUI as this is the same code path.

Yes this is possible. In the case of HVM based Xen DomUs ( which use Qemu, and have a disk images for each DomU) you should extract the disk image, and import the disk image using qm importdisk. See the pve reference documentation about importing from foreign hypervisors Users have reported...

it's normal to see some ethernet frames for others VMs when the vmbr0 bridge is learning otherwise you have to be more specific

what is the out of free -h and slabtop before you need to flush the caches ?

Did you cross post on https://pve.proxmox.com/pipermail/pve-user/2017-October/168937.html ?

We display a list of storages because you configured them on your system. Hiding a storage here would be as counterintuitive hiding as disk from your system because the disk is small. What I recommend you it to have a look at the "Folder View" in the Combox over the ressource tree, so that you...

reset SuperSpeed USB device number 2 ... this klnd of errors happen and resetting happen when lowlevel commands USB/ATA are not answered in a timely manner by your USB or disk device most probably a USB cable / device, the pve backup itself is probably fine, it's just that your target device...