Search results

With my current vm load, backups typically take an hour (for all vms) and restores dont' take that long either. The only thing that takes a long time is really pruning & verifying. At this point I think I'm going to just leave it as is. There is no "TCO" or "hourly work rate" as I just run...

16TB of ssd storage isn't exactly affordable/cheap....

Is it possible to qualify major? Am I better off having 20 3TB sas 7200 spindles over 10Gbit/s CIFS or like 2 sata 8TB drives locally in raid1? My backups in general run decently. Prunes & enumerating 4000+ backups in the webui take quite a while though.

I'd like to know this as well. I have manually put mounts in fstab & then pointed to those...but an official solution would be cleaner :)

I have the same issue. I don't have a PS2 port. I had to force legacy boot for the keyboard to work.

For those of you who are confused a bit on this as I was, here is an example: root@pbs:/# proxmox-backup-client change-owner vm/104 <youruser>@pbs --repository <yourrepository> the "group" can be seen in the gui under your datastore. My "backup groups" were "vm/104", "vm/105" etc... My...

That worked, thanks! I'm not super knowledgeable in the "new" systemd....so appreciate it. Is there any way to remove a datastore & unmount a disk from the gui? IIRC I removed the datastore from the CLI with the proxmox-backup-manager utility but had to stop a proxmox service first before...

I found this: mnt-datastore-001.mount Just rm it & I'm done?

Hello, and thank you for a great product! Recently I switched from local storage to CIFS mount & used a "sync job" to sync from local disk (datastore "001") to cifs (datastore "002"). Everything worked great. All files verified on the CIFS mount. I then ran "proxmox-backup-manager datastore...

I'm guessing you are out of loop devices... Do you run into the same issue if you use local storage with LVM? What does losetup -f show?

VGA info: root@vm2:~# lspci -s 05:00.0 05:00.0 VGA compatible controller: NVIDIA Corporation GF106GL [Quadro 2000] (rev a1) root@vm2:~# lspci -s 05:00.1 05:00.1 Audio device: NVIDIA Corporation GF106 High Definition Audio Controller (rev a1) vm config (with vga commented out): root@vm2:~# more...

Hi all, I've had a windows 10 vm with Quadro 2000 card passed through working perfectly on & off foro 2 weeks. Now, after rebooting it a few times the vm will no longer start. "qm start <vmid>" from the CLI gives hangs for a minute or two and then gives me: can't deactivate LV...

I know this is late, but I've done live migration without 'shared storage' by doing shared LVM on top of DRBD on top of local disk. The storage at the bottom of the stack was all local disk. This works very well actually.

It's an Asrock 890FX Deluxe4. dmesg says it negotiated a 6Gbit/s sata link with the 6Gbit port it's on (I"m using the SB sata chipset, not the marvell stuff).Open to any suggestions.

I'm not sure what you are trying to show me. All I know is that keeping all bios settings/hardware the same, my ssd is running at 1/4 sequential speed when not on 3.10. Is that a bug? I'd really like to run on 2.6.32 to have access to openvz

I'm reading directly from the device with my dd command so bypassing the filesystem. I just installed the 3.10 proxmox kernel & this improved my read speeds to ~ 450MB/s. Significantly better than 130M/second. My pveperf buffered reads went to 360M/second but my fsyncs went to 45.8/s ...?

Hello,I recently built a new Proxmox VE server with 3.1/2.6.32 and a seagate S600 SSD.The performance just doesn't seem very good. pveperf gives me 3k fsync/s but only 130M/s reading rate.If I do a "dd if=/dev/sda of=/dev/null bs=1M" my read rate is also 130MB.Changing nothing & booting into an...

I've seen this same behavior several years ago in ubuntu when I was troubleshooting something. Fixing it required re-enabling acpi....

This fixed my issue! Thank you very much!

Hey Udo, thanks for the help. Booting in single user mode showed the raid drive STILL as sda, so the "diskless" was only a symptom. The drive changing letters wasn't the cause. What _was_ the cause was lvm grabbing it before drbd. I fixed this by updating my filter to include "r|/dev/sda1|"...